public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30318] VRP does not create ANTI_RANGEs on overflow
Date: Sat, 05 May 2012 13:29:00 -0000 [thread overview]
Message-ID: <bug-30318-4-qWEDotYWK9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-30318-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30318
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |paolo.carlini at oracle dot
| |com
--- Comment #10 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-05-05 13:27:43 UTC ---
Now for the testcases... ;) Seriously, I have no idea what's the "policy" about
this kind of optimization, how many testcases are normally added, in principle
if one wanted to minimally exercise every code path would be dozens, I guess.
Personally I would be more interested in knowing how many times the new code
triggers in eg, a bootstrap.
next prev parent reply other threads:[~2012-05-05 13:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-30318-4@http.gcc.gnu.org/bugzilla/>
2011-12-22 3:25 ` pinskia at gcc dot gnu.org
2011-12-22 3:26 ` DMueller at suse dot com
2012-04-28 13:18 ` marc.glisse at normalesup dot org
2012-05-02 8:23 ` rguenther at suse dot de
2012-05-02 14:34 ` marc.glisse at normalesup dot org
2012-05-04 21:47 ` glisse at gcc dot gnu.org
2012-05-05 13:28 ` glisse at gcc dot gnu.org
2012-05-05 13:29 ` paolo.carlini at oracle dot com [this message]
2012-05-05 13:44 ` glisse at gcc dot gnu.org
2012-05-05 14:38 ` glisse at gcc dot gnu.org
2012-05-07 8:54 ` rguenther at suse dot de
2012-05-07 9:36 ` paolo.carlini at oracle dot com
2012-05-07 13:56 ` rguenth at gcc dot gnu.org
2012-05-07 14:47 ` glisse at gcc dot gnu.org
2012-06-20 12:01 ` rguenth at gcc dot gnu.org
2012-06-20 12:06 ` rguenth at gcc dot gnu.org
2012-06-20 19:13 ` glisse at gcc dot gnu.org
2012-07-25 18:27 ` glisse at gcc dot gnu.org
2012-07-29 14:45 ` glisse at gcc dot gnu.org
2012-08-03 12:22 ` glisse at gcc dot gnu.org
2012-08-03 12:36 ` glisse at gcc dot gnu.org
2012-08-03 12:53 ` rguenth at gcc dot gnu.org
2006-12-28 13:28 [Bug tree-optimization/30318] New: VRP does not create ANIT_RANGEs " rguenth at gcc dot gnu dot org
2006-12-28 19:35 ` [Bug tree-optimization/30318] VRP does not create ANTI_RANGEs " rguenth at gcc dot gnu dot org
2006-12-28 20:33 ` rguenth at gcc dot gnu dot 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-30318-4-qWEDotYWK9@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).