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 lto/40758] [LTO] ICE in partition_view_bitmap, at tree-ssa-live.c:331
Date: Wed, 26 Aug 2009 10:55:00 -0000	[thread overview]
Message-ID: <20090826105446.16745.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40758-11406@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from rguenth at gcc dot gnu dot org  2009-08-26 10:54 -------
The issue here is that during linking we do not optimize which triggers the
path in out-of-ssa coalescing that assumes no overlapping life-ranges are
present.  Which is obviously not true if we optimized during lto generation.

So this is really a middle-end problem.  Honza - what do you suggest to do
here?


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu dot
                   |                            |org


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


  parent reply	other threads:[~2009-08-26 10:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  2:29 [Bug lto/40758] New: " rmansfield at qnx dot com
2009-07-15  2:30 ` [Bug lto/40758] " rmansfield at qnx dot com
2009-07-15 10:54 ` rguenth at gcc dot gnu dot org
2009-07-15 12:58 ` rmansfield at qnx dot com
2009-07-15 13:02 ` rmansfield at qnx dot com
2009-07-15 15:17 ` rguenth at gcc dot gnu dot org
2009-07-17 14:53 ` rguenth at gcc dot gnu dot org
2009-07-17 15:12 ` rguenth at gcc dot gnu dot org
2009-08-26 10:55 ` rguenth at gcc dot gnu dot org [this message]
2009-09-26  1:35 ` matz at gcc dot gnu dot org
2009-09-26 16:47 ` matz at gcc dot gnu dot org
2009-09-28 20:41 ` hjl at gcc dot gnu dot org
2009-09-30 15:26 ` 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=20090826105446.16745.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).