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 tree-optimization/44562] [4.6 Regression] ICE: in get_alias_set, at alias.c:716 with -flto -fstrict-aliasing -fgraphite-identity
Date: Wed, 25 Aug 2010 12:36:00 -0000	[thread overview]
Message-ID: <20100825123637.8176.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44562-14164@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from rguenth at gcc dot gnu dot org  2010-08-25 12:36 -------
So the issue is that when we prime the streamer cache for lto-out we register
the common type nodes (lto_record_common_node) which changes TYPE_CANONICAL
in a way we don't like (it globs int and long int, or long int and long long
int
dependent on whether you are on 32bit or 64bit platforms).  This is done
to for example allow mixing of -f[un]signed-char units at link time.

I have a patch.


-- 


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


  parent reply	other threads:[~2010-08-25 12:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 21:02 [Bug tree-optimization/44562] New: " zsojka at seznam dot cz
2010-06-16 21:04 ` [Bug tree-optimization/44562] " zsojka at seznam dot cz
2010-06-16 22:18 ` rguenth at gcc dot gnu dot org
2010-06-17 13:51 ` [Bug tree-optimization/44562] [4.6 Regression] " zsojka at seznam dot cz
2010-06-24 21:35 ` rguenth at gcc dot gnu dot org
2010-06-30 15:54 ` jamborm at gcc dot gnu dot org
2010-07-02 12:28 ` jamborm at gcc dot gnu dot org
2010-07-23 12:03 ` rguenth at gcc dot gnu dot org
2010-08-23 20:12 ` rguenth at gcc dot gnu dot org
2010-08-24  2:02 ` pinskia at gcc dot gnu dot org
2010-08-25  0:37 ` t66667 at gmail dot com
2010-08-25 12:36 ` rguenth at gcc dot gnu dot org [this message]
2010-08-25 14:05 ` rguenth at gcc dot gnu dot org
2010-08-25 14:06 ` 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=20100825123637.8176.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).