public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/50082] -Wstrict-overflow mishandles typedef
Date: Tue, 16 Aug 2011 09:19:00 -0000 [thread overview]
Message-ID: <bug-50082-4-lCM36t82SI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50082-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50082
--- Comment #6 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-08-16 09:10:12 UTC ---
(In reply to comment #5)
> "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> writes:
>
> > I suppose the forwprop code wants to force a warning at -Wstrict-overflow=1
> > if the conditional becomes optimized to a constant at compile-time?
>
> Yes. But perhaps it is overly aggressive--are these conditionals being
> optimized to a constant? Maybe the condition for the first argument to
> fold_undefer_overflow_warnings needs to be fixed.
In this case not. forwprop doesn't do anything more fancy than calling
fold, so fold should already handle optimizing to a constant specially, no?
So I guess the first argument to fold_undefer_overflow_warnings should be
zero? I'll be posting a patch and CC you.
next prev parent reply other threads:[~2011-08-16 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 8:01 [Bug c/50082] New: " eggert at gnu dot org
2011-08-15 11:05 ` [Bug c/50082] " rguenth at gcc dot gnu.org
2011-08-15 14:48 ` ian at airs dot com
2011-08-15 15:09 ` rguenth at gcc dot gnu.org
2011-08-15 15:48 ` rguenth at gcc dot gnu.org
2011-08-15 20:04 ` iant at google dot com
2011-08-16 9:19 ` rguenth at gcc dot gnu.org [this message]
2011-08-16 11:47 ` [Bug tree-optimization/50082] " rguenth at gcc dot gnu.org
2011-08-16 15:36 ` rguenth at gcc dot gnu.org
2011-08-16 16:21 ` rguenth at gcc dot gnu.org
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=bug-50082-4-lCM36t82SI@http.gcc.gnu.org/bugzilla/ \
--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).