public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at pci dot uzh.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47566] ICE in vn_reference_lookup
Date: Tue, 01 Feb 2011 12:23:00 -0000 [thread overview]
Message-ID: <bug-47566-4-YCQp6hMpxB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47566-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47566
--- Comment #5 from Joost VandeVondele <Joost.VandeVondele at pci dot uzh.ch> 2011-02-01 12:23:35 UTC ---
(In reply to comment #4)
> That's indeed invalid - it should be an SSA name. This means some
> earlier pass messed up (or PRE itself). The bug shouldn't depend
> on LTO (apart from maybe requiring some cross-module inlining to trigger).
The same problem doesn't happen without LTO (but otherwise compiled with the
same options). I guess it needs the cross-module inlining.
I'll be uploading a tgz with sources.
next prev parent reply other threads:[~2011-02-01 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 9:38 [Bug middle-end/47566] New: " Joost.VandeVondele at pci dot uzh.ch
2011-02-01 9:42 ` [Bug middle-end/47566] " Joost.VandeVondele at pci dot uzh.ch
2011-02-01 11:53 ` rguenth at gcc dot gnu.org
2011-02-01 12:04 ` Joost.VandeVondele at pci dot uzh.ch
2011-02-01 12:12 ` rguenth at gcc dot gnu.org
2011-02-01 12:23 ` Joost.VandeVondele at pci dot uzh.ch [this message]
2011-02-01 12:29 ` Joost.VandeVondele at pci dot uzh.ch
2011-02-01 14:47 ` rguenth at gcc dot gnu.org
2011-02-01 14:54 ` Joost.VandeVondele at pci dot uzh.ch
2011-02-01 15:36 ` rguenth at gcc dot gnu.org
2011-02-01 15:40 ` rguenth at gcc dot gnu.org
2011-02-01 15:52 ` Joost.VandeVondele at pci dot uzh.ch
2011-02-01 21:23 ` Joost.VandeVondele at pci dot uzh.ch
2011-02-02 9:59 ` rguenth at gcc dot gnu.org
2011-02-02 10:00 ` rguenth at gcc dot gnu.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=bug-47566-4-YCQp6hMpxB@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).