public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/10175: [3.3/3.4 regression] -Wunreachable-code broken
@ 2003-04-03 22:07 jason
  0 siblings, 0 replies; 2+ messages in thread
From: jason @ 2003-04-03 22:07 UTC (permalink / raw)
  To: bobsummerwill, gcc-bugs, gcc-prs, jason, nobody

Synopsis: [3.3/3.4 regression] -Wunreachable-code broken

Responsible-Changed-From-To: unassigned->jason
Responsible-Changed-By: jason
Responsible-Changed-When: Thu Apr  3 22:06:59 2003
Responsible-Changed-Why:
    got it

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10175


^ permalink raw reply	[flat|nested] 2+ messages in thread
* Re: c/10175: [3.3/3.4 regression] -Wunreachable-code broken
@ 2003-03-21  1:35 bangerth
  0 siblings, 0 replies; 2+ messages in thread
From: bangerth @ 2003-03-21  1:35 UTC (permalink / raw)
  To: bobsummerwill, gcc-bugs, gcc-prs, nobody

Old Synopsis: -Wunreachable-code appears broken for one-line blocks.
New Synopsis: [3.3/3.4 regression] -Wunreachable-code broken

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Fri Mar 21 01:35:59 2003
State-Changed-Why:
    Confirmed, the warning is only displayed for the
    multi-statement block.
    
    However, what is worse: for 3.3 and present mainline, the
    warning isn't generated _at all_, so this is a regression.
    All this is the same for the C and C++ front ends, by the
    way, so I put it into the more generic "C" category.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10175


^ permalink raw reply	[flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-04-03 22:07 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-03 22:07 c/10175: [3.3/3.4 regression] -Wunreachable-code broken jason
  -- strict thread matches above, loose matches on Subject: below --
2003-03-21  1:35 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).