public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/9211: [3.2 regression] Compiler segfault upon use of __noreturn__ function in static initializer
@ 2003-03-10 11:43 reichelt
0 siblings, 0 replies; 2+ messages in thread
From: reichelt @ 2003-03-10 11:43 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, kendall, nobody
Synopsis: [3.2 regression] Compiler segfault upon use of __noreturn__ function in static initializer
State-Changed-From-To: analyzed->closed
State-Changed-By: reichelt
State-Changed-When: Mon Mar 10 11:43:00 2003
State-Changed-Why:
Fixed.
This is actually a duplicate of PR 6794.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9211
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: c++/9211: [3.2 regression] Compiler segfault upon use of __noreturn__ function in static initializer
@ 2003-01-07 2:15 bangerth
0 siblings, 0 replies; 2+ messages in thread
From: bangerth @ 2003-01-07 2:15 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, kendall, nobody
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-03-10 11:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-10 11:43 c++/9211: [3.2 regression] Compiler segfault upon use of __noreturn__ function in static initializer reichelt
-- strict thread matches above, loose matches on Subject: below --
2003-01-07 2:15 bangerth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).