public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kazu at cs dot umass dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/21289] New: A numeric range is spoiled by a symblic one in VRP Date: Fri, 29 Apr 2005 19:14:00 -0000 [thread overview] Message-ID: <20050429191405.21289.kazu@cs.umass.edu> (raw) Consider int foo (int a, int b) { if (a == 1) if (a < b) if (a == 1) return 1; return 0; } VRP does not remove the third "if" even though 'a' is known to be 1. This is because the symbolic range obtained from the second "if" spoils the numeric range [1, 1] obtained from the first "if". extract_range_from_assert tries to refine a range from an ASSERT_EXPR if there is another range previously available, but in this case, VRP cannot prove that [1,1] and [-INF, b-1] intersects, it does not refine a range. -- Summary: A numeric range is spoiled by a symblic one in VRP Product: gcc Version: unknown Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: kazu at cs dot umass dot edu CC: dnovillo at redhat dot com,gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21289
next reply other threads:[~2005-04-29 19:14 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-29 19:14 kazu at cs dot umass dot edu [this message] 2005-04-29 19:28 ` [Bug tree-optimization/21289] " pinskia at gcc dot gnu dot org 2005-04-29 20:37 ` dberlin at gcc dot gnu dot org 2005-05-14 19:40 ` kazu at cs dot umass dot edu 2005-05-14 20:00 ` dnovillo at redhat dot com 2005-06-02 2:59 ` cvs-commit at gcc dot gnu dot org 2005-06-02 3:08 ` dnovillo at gcc dot gnu dot org 2005-06-02 18:46 ` pinskia 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=20050429191405.21289.kazu@cs.umass.edu \ --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: linkBe 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).