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 tree-optimization/25643] VRP does not remove -fbounds-check for Fortran
Date: Fri, 29 Jun 2012 13:23:00 -0000	[thread overview]
Message-ID: <bug-25643-4-Pla2OP5dfy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-25643-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |NEW

--- Comment #13 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-06-29 13:23:15 UTC ---
(In reply to comment #5)
> Grrr:
> Visiting PHI node: i_3 = PHI <i_17(4), i_13(13)>;
>     Argument #0 (4 -> 12 executable)
>         i_17
>         Value: [1, 1]  EQUIVALENCES: { } (0 elements)
> 
>     Argument #1 (13 -> 12 executable)
>         i_13
>         Value: [2, +INF]  EQUIVALENCES: { } (0 elements)
> 
> so we have [1,1] UNION [2, +INF] and we just get ~[0,0] bogus
> and it also means this is PR 23744.

This is now fixed but the rest still applies.


       reply	other threads:[~2012-06-29 13:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-25643-4@http.gcc.gnu.org/bugzilla/>
2012-06-29 13:23 ` rguenth at gcc dot gnu.org [this message]
2023-09-03  3:24 ` pinskia at gcc dot gnu.org
2006-01-02 19:54 [Bug tree-optimization/25643] New: VRP does not remove -fbounds-checking " pinskia at gcc dot gnu dot org
2006-01-02 20:23 ` [Bug tree-optimization/25643] VRP does not remove -fbounds-check " pinskia at gcc dot gnu dot org
2006-01-03 20:37 ` pinskia at gcc dot gnu dot org
2006-01-07 16:20 ` pinskia at gcc dot gnu dot org
2006-01-29 21:05 ` pinskia at gcc dot gnu dot org
2006-05-01  6:18 ` pinskia at gcc dot gnu dot org
2006-05-01 10:09 ` baldrick at free dot fr
2008-01-12 12:48 ` rguenth at gcc dot gnu dot org
2008-01-12 12:49 ` rguenth at gcc dot gnu dot org
2008-01-12 13:06 ` rguenth at gcc dot gnu dot org
2008-01-12 13:17 ` pinskia at gcc dot gnu dot org
2008-01-12 13:35 ` pinskia at gcc dot gnu dot org
2008-01-12 13:53 ` pinskia at gcc dot gnu dot org
2008-01-12 15:15 ` rguenth at gcc dot gnu dot org
2008-03-14 16:40 ` 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-25643-4-Pla2OP5dfy@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).