public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/31710] [4.2/4.3 Regression] ICE in in set_value_range, at tree-vrp.c:278
Date: Thu, 26 Apr 2007 08:05:00 -0000	[thread overview]
Message-ID: <20070426080527.15062.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31710-3760@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from pinskia at gcc dot gnu dot org  2007-04-26 09:05 -------
So the range in an semi-old (3 days) compiler, we get is:
D.1602_2: VARYING
D.1602_3: [-32768, -32768]  EQUIVALENCES: { D.1602_2 D.1602_8 } (2 elements)
D.1603_4: [-INF(OVF), -32768]  EQUIVALENCES: { } (0 elements)
D.1602_8: [-32768, -32768]  EQUIVALENCES: { D.1602_2 } (1 elements)

Well obviously the recent patch to tree-vrp.c (which was also applied to the
4.2 branch) caused this failure as we are checking for overflow in some cases. 
I always said the patch should never have been applied to the 4.2 branch
without a lot more testing.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ian at gcc dot gnu dot org
           Severity|normal                      |blocker
  GCC build triplet|x86_64-unknown-linux-gnu    |
   GCC host triplet|x86_64-unknown-linux-gnu    |
 GCC target triplet|x86_64-unknown-linux-gnu    |
           Keywords|                            |ice-checking, ice-on-valid-
                   |                            |code
            Summary|ICE in in set_value_range,  |[4.2/4.3 Regression] ICE in
                   |at tree-vrp.c:278           |in set_value_range, at tree-
                   |                            |vrp.c:278
   Target Milestone|---                         |4.2.0


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


  parent reply	other threads:[~2007-04-26  8:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26  7:46 [Bug c/31710] New: " marcus at jet dot franken dot de
2007-04-26  7:46 ` [Bug c/31710] " marcus at jet dot franken dot de
2007-04-26  8:05 ` pinskia at gcc dot gnu dot org [this message]
2007-04-27  3:52 ` [Bug middle-end/31710] [4.2/4.3 Regression] " ian at airs dot com
2007-04-27 20:47 ` ian at gcc dot gnu dot org
2007-04-27 20:49 ` ian at gcc dot gnu dot org
2007-04-27 20:51 ` ian at airs dot com
2007-04-28 21:48 ` pinskia at gcc dot gnu dot org
2007-04-29 19:19 ` mstein at phenix dot rootshell dot be
2007-05-01 16:59 ` mstein at phenix dot rootshell dot be
2007-05-01 17:58 ` ian at airs dot com

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=20070426080527.15062.qmail@sourceware.org \
    --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).