public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/37526] [4.4 Regression] ICE using --combine -O2
Date: Tue, 16 Sep 2008 13:31:00 -0000	[thread overview]
Message-ID: <20080916132952.6386.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37526-12684@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from pinskia at gmail dot com  2008-09-16 13:29 -------
Subject: Re:  [4.4 Regression] ICE using --combine -O2



Sent from my iPhone

On Sep 16, 2008, at 6:20 AM, "rguenth at gcc dot gnu dot org"
<gcc-bugzilla@gcc.gnu.org 
 > wrote:

>
>
> ------- Comment #7 from rguenth at gcc dot gnu dot org  2008-09-16  
> 13:20 -------
> ./cc1 -quiet -O2 t1.i t2.i
> t2.i: In function 'Node_print':
> t2.i:2: error: non-trivial conversion at assignment
> struct _IO_FILE *
> struct _IO_FILE *
> # LOADS:  { stderr }
> stderr.0_3 = stderr;
>
> t2.i:2: error: non-trivial conversion at assignment
> struct _IO_FILE *
> struct _IO_FILE *
> # LOADS:  { stderr }
> stderr.0_4 = stderr;
>

No those two types should compatible. If they are not then there is a  
bug in the middle-end. I think this is why there was the Lang hook in  
the first place.

> t2.i:2: internal compiler error: verify_stmts failed
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://gcc.gnu.org/bugs.html> for instructions.
>
>
> So we have wrong GIMPLE here.  GIGO.
>
> Value numbering stderr.0_3 stmt = stderr.0_3 = stderr;
> Setting value number of stderr.0_3 to stderr.0_3
> ...
> Value numbering stderr.0_4 stmt = stderr.0_4 = stderr;
> Inserting name stderr.0_17 for expression (struct _IO_FILE *) stderr. 
> 0_3
> Setting value number of stderr.0_4 to stderr.0_17
>
>
> -- 
>
> rguenth at gcc dot gnu dot org changed:
>
>           What    |Removed                     |Added
> --- 
> --- 
> ----------------------------------------------------------------------
>                 CC|                            |rguenth at gcc dot  
> gnu dot
>                   |                            |org
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37526
>


-- 


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


  parent reply	other threads:[~2008-09-16 13:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15 19:00 [Bug c/37526] New: " patrik dot hagglund at bredband dot net
2008-09-15 19:02 ` [Bug c/37526] " patrik dot hagglund at bredband dot net
2008-09-15 19:03 ` patrik dot hagglund at bredband dot net
2008-09-15 19:04 ` patrik dot hagglund at bredband dot net
2008-09-15 19:05 ` [Bug middle-end/37526] " patrik dot hagglund at bredband dot net
2008-09-15 19:12 ` [Bug tree-optimization/37526] " pinskia at gcc dot gnu dot org
2008-09-15 19:39 ` [Bug tree-optimization/37526] [4.4 Regression] " pinskia at gcc dot gnu dot org
2008-09-16 13:21 ` rguenth at gcc dot gnu dot org
2008-09-16 13:29   ` Andrew Thomas Pinski
2008-09-16 13:31 ` pinskia at gmail dot com [this message]
2008-10-22  3:20 ` mmitchel at gcc dot gnu dot org
2008-10-27 10:48 ` jakub at gcc dot gnu dot org
2008-10-27 11:23 ` jakub 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=20080916132952.6386.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).