[Bug libstdc++/14493] std::bad_alloc::what() does not explain what happened

2007-01-31 Thread lopresti at gmail dot com
--- 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 improv

[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

2007-01-31 Thread pinskia at gcc dot gnu dot org
--- 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

[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

2007-01-31 Thread zippel at linux-m68k dot org
--- 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_