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 lto/55525] ICE: tree check: expected array_type, have pointer_type in array_ref_low_bound, at expr.c:6768
Date: Thu, 29 Nov 2012 08:53:00 -0000	[thread overview]
Message-ID: <bug-55525-4-bz2ZZfldTc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55525-4@http.gcc.gnu.org/bugzilla/>


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2012-11-29
         AssignedTo|unassigned at gcc dot       |rguenth at gcc dot gnu.org
                   |gnu.org                     |
     Ever Confirmed|0                           |1

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> 2012-11-29 08:53:09 UTC ---
Mine.

I suppose we could simply error out for the mismatch.  The issue here is of
course that we simply substitute the prevailing declaration into expressions
that expect the mismatching type.

Let me think a bit more about this.


  parent reply	other threads:[~2012-11-29  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29  2:53 [Bug lto/55525] New: " d.g.gorbachev at gmail dot com
2012-11-29  2:55 ` [Bug lto/55525] " d.g.gorbachev at gmail dot com
2012-11-29  3:07 ` d.g.gorbachev at gmail dot com
2012-11-29  8:53 ` rguenth at gcc dot gnu.org [this message]
2012-12-05  8:48 ` rguenth at gcc dot gnu.org
2012-12-05  9:33 ` rguenth at gcc dot gnu.org
2013-01-07 14:48 ` ro at gcc dot gnu.org
2013-01-07 14:56 ` rguenther at suse dot de

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-55525-4-bz2ZZfldTc@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).