public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/4210] should not warning with dead code
Date: Wed, 01 Mar 2006 23:01:00 -0000	[thread overview]
Message-ID: <20060301230141.13253.qmail@sourceware.org> (raw)
In-Reply-To: <bug-4210-955@http.gcc.gnu.org/bugzilla/>



------- Comment #13 from joseph at codesourcery dot com  2006-03-01 23:01 -------
Subject: Re:  should not warning with dead code

A workaround is to use ? : and statement expressions instead of "if".  
This way, the front-end setting of skip_evaluation disables these 
warnings.  (skip_evaluation can't be set for if (0) because you can jump 
into if (0), whereas jumps into statement expressions are not permitted.  
Thus in general you need to parse the whole function body to tell if the 
if (0) is dead.)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=4210


  parent reply	other threads:[~2006-03-01 23:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-4210-955@http.gcc.gnu.org/bugzilla/>
2006-03-01 19:02 ` pinskia at gcc dot gnu dot org
2006-03-01 23:01 ` joseph at codesourcery dot com [this message]
2006-03-01 23:05 ` bangerth at dealii dot org
2006-03-01 23:22 ` joseph at codesourcery dot com
2006-03-01 23:25 ` bangerth at dealii dot org
2006-03-02  9:22 ` mattias at virtutech dot se
2006-06-20 19:08 ` pinskia at gcc dot gnu dot org
2007-01-01 19:03 ` pinskia at gcc dot gnu dot org
2009-05-12 14:50 ` pinskia at gcc dot gnu dot org
2010-07-06 17:24 ` manu at gcc dot gnu dot org
2010-07-06 17:28 ` manu at gcc dot gnu dot org
     [not found] <bug-4210-4@http.gcc.gnu.org/bugzilla/>
2014-03-13  2:10 ` pinskia at gcc dot gnu.org
2014-08-09  6:09 ` pinskia at gcc dot gnu.org
2020-04-26 21:28 ` nisse at lysator dot liu.se
2020-05-04 20:44 ` nisse at lysator dot liu.se
2020-05-05  2:17 ` vincent-gcc at vinc17 dot net

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=20060301230141.13253.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).