[Bug tree-optimization/30911] New: VRP fails to eliminate range checks in Ada code

public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed

From: "baldrick at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30911]  New: VRP fails to eliminate range checks in Ada code
Date: Wed, 21 Feb 2007 13:57:00 -0000	[thread overview]
Message-ID: <bug-30911-13647@http.gcc.gnu.org/bugzilla/> (raw)

All of the range checks can in theory be eliminated, except
for the first one (a call to __gnat_rcheck_04, unlike the
others which are calls to __gnat_rcheck_04), but they are
not:

$ gcc -c -O2 -fdump-tree-all j.ads
$ grep __gnat_rcheck_12 j.ads.118t.final_cleanup
  __gnat_rcheck_12 ("join_equal.adb", 14);
  __gnat_rcheck_12 ("join_equal.adb", 14);
  __gnat_rcheck_12 ("join_equal.adb", 29);
  __gnat_rcheck_12 ("join_equal.adb", 29);
  __gnat_rcheck_12 ("join_equal.adb", 39);
  __gnat_rcheck_12 ("join_equal.adb", 39);


-- 
           Summary: VRP fails to eliminate range checks in Ada code
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: baldrick at gcc dot gnu dot org
  GCC host triplet: i486-linux-gnu


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

next             reply	other threads:[~2007-02-21 13:57 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 13:57 baldrick at gcc dot gnu dot org [this message]
2007-02-21 15:18 ` [Bug tree-optimization/30911] " baldrick at gcc dot gnu dot org
2007-02-21 17:55 ` steven at gcc dot gnu dot org
2007-02-21 18:01 ` ebotcazou at gcc dot gnu dot org
2007-02-22 17:04 ` rguenth at gcc dot gnu dot org
2007-02-22 17:33 ` ebotcazou at gcc dot gnu dot org
2007-02-22 17:41 ` baldrick at gcc dot gnu dot org
2007-02-22 18:01 ` ebotcazou at gcc dot gnu dot org
2007-02-22 18:14 ` baldrick at gcc dot gnu dot org
2007-02-22 18:18 ` baldrick at gcc dot gnu dot org
2007-02-22 18:19 ` ebotcazou at gcc dot gnu dot org
2007-02-22 22:54 ` baldrick at gcc dot gnu dot org
2007-02-23  5:50 ` ebotcazou at gcc dot gnu dot org
2007-02-23  9:22 ` rguenth at gcc dot gnu dot org
2007-02-23  9:39 ` baldrick at free dot fr
2007-02-23 10:03 ` baldrick at free dot fr
2007-02-23 11:37 ` rguenth at gcc dot gnu dot org
2007-02-23 11:42 ` rguenth at gcc dot gnu dot org
2007-02-23 12:36 ` baldrick at free dot fr
2007-02-23 12:41 ` rguenth at gcc dot gnu dot org
2007-02-23 13:05 ` baldrick at free dot fr
2007-02-23 14:05 ` rguenth at gcc dot gnu dot org
2007-02-23 15:15 ` rguenth at gcc dot gnu dot org
2007-02-23 15:40 ` baldrick at free dot fr
2007-02-23 15:55 ` rguenth at gcc dot gnu dot org
2007-02-23 15:59 ` baldrick at free dot fr
2007-02-23 16:01 ` baldrick at free dot fr
2007-02-23 16:05 ` charlet at gcc dot gnu dot org
2007-02-23 16:11 ` rguenth at gcc dot gnu dot org
2007-02-23 17:09 ` baldrick at free dot fr
2007-02-23 17:33 ` rguenth at gcc dot gnu dot org
2007-02-23 20:18 ` rguenth at gcc dot gnu dot org
2007-02-23 22:40 ` rguenth at gcc dot gnu dot org
2007-02-24 10:12   ` Arnaud Charlet
2007-02-24 12:32     ` Arnaud Charlet
2007-02-24 10:12 ` charlet at adacore dot com
2007-02-24 12:32 ` charlet at adacore dot com
2007-02-24 12:38 ` rguenth at gcc dot gnu dot org
2007-02-24 12:47   ` Arnaud Charlet
2007-02-24 12:48 ` charlet at adacore dot com
2007-02-28 23:30 ` baldrick at free dot fr
2007-03-01  8:18 ` baldrick at free dot fr
2007-03-01  9:50 ` rguenth at gcc dot gnu dot org
2007-03-01 23:07 ` baldrick at free dot fr
2007-03-02  9:02 ` rguenth at gcc dot gnu dot org
2007-03-02  9:16 ` baldrick at free dot fr
2007-03-02  9:53 ` rguenth at gcc dot gnu dot org
2008-03-28 12:21 ` rguenth at gcc dot gnu dot org
2008-03-28 14:59 ` baldrick at gcc dot gnu dot org
2008-03-28 19:19 ` rguenth at gcc dot gnu dot org
2008-03-28 22:13 ` rguenth at gcc dot gnu dot org
2008-03-28 22:15 ` rguenth at gcc dot gnu dot org
2008-03-28 22:36 ` rguenth at gcc dot gnu dot org
2008-03-28 22:43 ` baldrick at free dot fr
2008-03-28 22:49 ` baldrick at free dot fr
2008-03-28 22:59 ` rguenth at gcc dot gnu dot org
2008-03-30  9:15 ` ebotcazou at gcc dot gnu dot org
2008-03-30 14:15 ` baldrick at gcc dot gnu dot org
2008-03-30 14:19 ` baldrick at gcc dot gnu dot org
2008-03-30 14:27 ` baldrick at free dot fr
2008-03-30 14:53 ` rguenther at suse dot de
2008-03-30 14:56 ` rguenth at gcc dot gnu dot org
2008-03-30 15:03 ` ebotcazou at gcc dot gnu dot org
2008-03-30 15:09 ` rguenth at gcc dot gnu dot org
2008-03-30 15:17 ` baldrick at free dot fr
2008-03-30 15:46 ` ebotcazou at gcc dot gnu dot org
2008-03-30 15:56 ` rguenther at suse dot de
2008-03-30 16:03 ` baldrick at free dot fr
2008-03-30 16:16 ` ebotcazou at gcc dot gnu dot org
2008-03-30 16:19 ` ebotcazou at gcc dot gnu dot org
2008-03-30 17:04 ` baldrick at free dot fr
2008-04-03 19:53 ` rguenth at gcc dot gnu dot org
2009-11-17 11:04 ` baldrick at free dot fr
2009-11-17 11:19 ` ebotcazou at gcc dot gnu dot org
2009-11-17 15:08 ` rguenther at suse dot de
2009-11-17 15:50   ` Arnaud Charlet
2009-11-17 15:50 ` charlet at adacore dot com
2009-11-17 16:57 ` baldrick at free dot fr
2009-11-17 17:03 ` charlet 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-30911-13647@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).