public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rcampbell@tropicnetworks.com
Subject: Re: c/8828: gcc reports some code is unreachable when it is not
Date: Fri, 06 Dec 2002 01:29:00 -0000	[thread overview]
Message-ID: <20021206092912.17797.qmail@sources.redhat.com> (raw)

Synopsis: gcc reports some code is unreachable when it is not

State-Changed-From-To: open->analyzed
State-Changed-By: reichelt
State-Changed-When: Fri Dec  6 01:29:11 2002
State-Changed-Why:
    Confirmed.
    
    An even shorter example is the following:
    
    -----------------snip here----------------
    void foo(int i)
    {
      switch(i) {
        case 0:
          break;
        case 1:
          break;
      }
    }
    -----------------snip here----------------
    
    Compiling this with gcc 3.2.1 or mainline I get the message
    
    PR8828.c: In function `foo':
    PR8828.c:7: warning: will never be executed
    PR8828.c:5: warning: will never be executed
    
    i.e. the compiler complains about the "break" statements.
    
    This is a regression from gcc 3.0.4 where the warning is not issued.

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


             reply	other threads:[~2002-12-06  9:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06  1:29 reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-06 17:06 Christian Ehrhardt
2002-12-06 15:56 Wolfgang Bangerth
2002-12-06  8:26 Rolf Campbell
2002-12-06  8:16 Christian Ehrhardt
2002-12-05 13:06 rcampbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021206092912.17797.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rcampbell@tropicnetworks.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).