public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30564] ice for legal code with -O3
Date: Tue, 23 Jan 2007 21:55:00 -0000	[thread overview]
Message-ID: <20070123215531.21724.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30564-9596@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from rguenth at gcc dot gnu dot org  2007-01-23 21:55 -------
Honza, we're not folding the comparison on inlining and later ICE in tree-vrp
because of this (from the einline dump):

  # fp1_5 = PHI <fp1_7(5), fp1_4(8), fp1_4(9)>
<L7>:;
  i_30 = fp0_6;
  goto <bb 14> (<L10>);

<L18>:;
  D.1689_35 = unicount[i_3];
  D.1690_36 = D.1689_35 == 0;
  D.1691_37 = i_3 != i_3;
  D.1692_38 = D.1690_36 && D.1691_37;
  if (D.1692_38) goto <L15>; else goto <L17>;

<L15>:;
  RawOrEnc = 1;


look at the i_3 != i_3


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
          Component|tree-optimization           |c
     Ever Confirmed|0                           |1
           Keywords|ice-on-valid-code           |
   Last reconfirmed|0000-00-00 00:00:00         |2007-01-23 21:55:31
               date|                            |
            Summary|[4.3 Regression] ice for    |ice for legal code with -O3
                   |legal code with -O3         |
   Target Milestone|4.3.0                       |---


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


  parent reply	other threads:[~2007-01-23 21:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 20:58 [Bug c/30564] New: " dcb314 at hotmail dot com
2007-01-23 21:00 ` [Bug c/30564] " dcb314 at hotmail dot com
2007-01-23 21:29 ` rguenth at gcc dot gnu dot org
2007-01-23 21:37 ` [Bug tree-optimization/30564] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-01-23 21:55 ` rguenth at gcc dot gnu dot org [this message]
2007-01-23 21:56 ` [Bug c/30564] " rguenth at gcc dot gnu dot org
2007-01-23 21:57 ` [Bug tree-optimization/30564] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-01-24  7:21 ` pinskia at gcc dot gnu dot org
2007-01-24  7:24 ` pinskia at gcc dot gnu dot org
2007-01-27 21:42 ` pinskia at gcc dot gnu dot org
2007-01-27 22:30 ` pinskia at gcc dot gnu dot org
2007-01-27 23:31 ` pinskia at gcc dot gnu dot org
2007-01-28  7:58 ` pinskia at gcc dot gnu dot org
2007-01-28 19:10 ` pinskia at gcc dot gnu dot org
2007-01-28 22:57 ` pinskia at gcc dot gnu dot org
2007-05-22 22:11 ` pinskia at gcc dot gnu dot org
2007-06-29 17:50 ` mmitchel at gcc dot gnu dot org
2007-08-19 19:07 ` pinskia at gcc dot gnu dot org
2007-08-19 19:19 ` pinskia at gcc dot gnu dot org
2007-08-20  7:43 ` pinskia at gcc dot gnu dot org
2007-08-20  7:43 ` 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=20070123215531.21724.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).