[Bug c++/30387] Broken code generation on if/else statement

2007-01-05 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2007-01-05 22:08 --- static std::auto_ptr throw_exception(GError* gobject) __attribute__((__noreturn__)); This is not a GCC bug because the function is marked as noreturn. -- pinskia at gcc dot gnu dot org changed: Wh

[Bug c++/30387] Broken code generation on if/else statement

2007-01-05 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-01-05 22:06 --- Are you sure that _ZN4Glib5Error15throw_exceptionEP7_GError (Glib::Error::throw_exception(_GError*) ) does not always throw an exception and is marked as noreturn? If that is the case then this is not a bug. --

[Bug c++/30387] Broken code generation on if/else statement

2007-01-05 Thread matt dot hoosier at gmail dot com
--- Comment #2 from matt dot hoosier at gmail dot com 2007-01-05 21:54 --- Test case is posted at http://www.cis.ksu.edu/~matt/pub/gcc_bug_30387.ii (~2 MB). Apologies for the large post, but the code generation bug wasn't triggered when all the imported types were stubbed out. --

[Bug c++/30387] Broken code generation on if/else statement

2007-01-05 Thread matt dot hoosier at gmail dot com
--- Comment #1 from matt dot hoosier at gmail dot com 2007-01-05 21:47 --- The GCC version in question here is the stock g++ shipped with Ubuntu edgy, but the bug has been observed on other (3.4.4 and 4.1.1) builds too. The test program (see attachment) is compiled with: g++ -Wall -