[Bug target/28183] [4.0/4.1/4.2/4.3 regression] assembler error "FATAL: can't close x.o" on m68k with new binutils
--- Comment #6 from zippel at linux-m68k dot org 2007-01-31 18:20 --- This bug can be closed, it's really a bug in binutils triggered by some inline assembly in cln. Here is a bit more info: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388000 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28183 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Bug target/28183] [4.0/4.1/4.2/4.3 regression] assembler error "FATAL: can't close x.o" on m68k with new binutils
--- Comment #7 from pinskia at gcc dot gnu dot org 2007-01-31 18:27 --- Marking as invalid as requested. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28183 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Bug libstdc++/14493] std::bad_alloc::what() does not explain what happened
--- Comment #26 from lopresti at gmail dot com 2007-02-01 02:17 --- I found this PR because I tried calling what() on a bad_alloc, was surprised by what I got, and did a search. This is my perspective as a random end user; make of it what you will. I think "std::bad_alloc" is an improvement. But I was actually expecting what() to provide something human readable and very specific, like "out of memory" or "heap corrupted". In my case, I already know the exception is a std::bad_alloc; I could generate that particular constant string myself... I find it remarkable that this PR is almost two years old. -- lopresti at gmail dot com changed: What|Removed |Added CC||lopresti at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14493 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
