This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/9211: [3.2 regression] Compiler segfault upon use of __noreturn__ function in static initializer
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, kendall at abinitio dot com, nobody at gcc dot gnu dot org
- Date: 7 Jan 2003 02:15:54 -0000
- Subject: Re: c++/9211: [3.2 regression] Compiler segfault upon use of __noreturn__ function in static initializer
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, kendall at abinitio dot com, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Old Synopsis: Compiler segfault upon use of __noreturn__ function in static initializer
New Synopsis: [3.2 regression] Compiler segfault upon use of __noreturn__ function in static initializer
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Mon Jan 6 18:15:53 2003
State-Changed-Why:
Confirmed. This is a regression on the 3.2 branch, it is
fixed for 3.3 and 3.4. It also worked for 3.0.
I guess the short answer for this is: don't do it. What
should the semantics be anyway for something like this?
However, it is a regression, so I leave it open while
the 3.2.x branch is still alive.
Thanks for your report
Wolfgang
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9211