public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <Joe.Buck@synopsys.COM>
To: Robert Dewar <dewar@adacore.com>
Cc: Dmitry Antipov <antipov@dev.rtsoft.ru>, gcc@gcc.gnu.org
Subject: Re: Dubious "'foo' might be used uninitialized in this function" message
Date: Wed, 15 Dec 2004 17:33:00 -0000	[thread overview]
Message-ID: <20041215092134.A25280@synopsys.com> (raw)
In-Reply-To: <41C0289C.2000209@adacore.com>; from dewar@adacore.com on Wed, Dec 15, 2004 at 07:05:48AM -0500

On Wed, Dec 15, 2004 at 07:05:48AM -0500, Robert Dewar wrote:
> Dmitry Antipov wrote:
> 
> >> it gets as complex as the halting problem :)
> > Really ? Why ?
> 
> Because the general evaluation of compile time contants
> is clearly in this territory. Your example:
> [ deleted ]
> 
> requires the compiler to do symbolic evaluation of the
> tests in lines 7 and 10 and determine that they always
> have the same truth value.

This case and many other common cases that gcc gives false reports
on could be solved by using a gated SSA approach (which would, as you
suggest, determine that the two tests have the same truth value).
However, using such an approach goes against the desire by many people
that the warnings they get at -O0 be the same as those for higher levels.

  parent reply	other threads:[~2004-12-15 17:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 15:23 Dmitry Antipov
2004-12-14 16:40 ` E. Weddington
2004-12-14 17:00 ` Nathan Sidwell
2004-12-15  9:00   ` Dmitry Antipov
2004-12-15 10:02     ` Nathan Sidwell
2004-12-15 12:06     ` Robert Dewar
2004-12-15 17:33       ` Florian Weimer
2004-12-15 17:34         ` Robert Dewar
2004-12-15 17:52           ` Florian Weimer
2004-12-15 18:00             ` Robert Dewar
2004-12-15 17:33       ` Joe Buck [this message]
2004-12-15 18:03         ` Dave Korn
2004-12-15 18:09           ` Robert Dewar

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=20041215092134.A25280@synopsys.com \
    --to=joe.buck@synopsys.com \
    --cc=antipov@dev.rtsoft.ru \
    --cc=dewar@adacore.com \
    --cc=gcc@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).