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/41159] [LTO] ICE in insert_value_copy_on_edge, at tree-outof-ssa.c:225
Date: Fri, 15 Apr 2011 10:33:00 -0000 [thread overview]
Message-ID: <bug-41159-4-9ZdoDvUs0h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41159-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41159
--- Comment #11 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-04-15 10:33:03 UTC ---
(In reply to comment #9)
> I believe I also have this occurring with host=x86_64-linux
> target=arm-linux-gnueabi. After reading this ticket, I retried my compiles
> with the same link and compile optimization level and it succeeds.
>
> I understand that you want gcc to support different option levels for both
> compile and link. However, I don't know that most people want this and I am
> not use to passing the linker options; a diagnostic for ld/gold plug-in when
> there is an optimization mismatch may be helpful? Is that a possibility for
> 4.5.x and 4.6.x releases?
It's not easy, otherwise we'd have done this already ;)
next prev parent reply other threads:[~2011-04-15 10:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41159-4@http.gcc.gnu.org/bugzilla/>
2010-12-10 13:10 ` ixt at nm dot ru
2011-04-14 21:57 ` bpringlemeir at gmail dot com
2011-04-14 22:00 ` bpringlemeir at gmail dot com
2011-04-15 10:33 ` rguenth at gcc dot gnu.org [this message]
2011-08-02 15:23 ` mh+gcc at glandium dot org
2011-12-14 23:47 ` pinskia at gcc dot gnu.org
2011-12-14 23:47 ` pinskia at gcc dot gnu.org
2011-12-14 23:48 ` pinskia at gcc dot gnu.org
2011-12-15 10:19 ` rguenth at gcc dot gnu.org
2011-12-15 14:06 ` ubizjak at gmail dot com
2011-12-15 14:16 ` ubizjak at gmail dot com
2011-12-20 11:02 ` rguenth at gcc dot gnu.org
2011-12-20 11:04 ` rguenth at gcc dot gnu.org
2011-12-20 12:31 ` rmansfield at qnx dot com
2011-12-21 7:54 ` ubizjak at gmail dot com
2011-12-21 9:24 ` rguenth at gcc dot gnu.org
2011-12-21 9:29 ` rguenth at gcc dot gnu.org
2011-12-21 12:44 ` uros at gcc dot gnu.org
2011-12-21 17:27 ` uros at gcc dot gnu.org
2011-12-21 18:31 ` ubizjak at gmail dot com
2009-08-24 19:28 [Bug lto/41159] New: " rmansfield at qnx dot com
2009-08-24 19:34 ` [Bug lto/41159] " rmansfield at qnx dot com
2009-10-03 22:14 ` rguenth at gcc dot gnu dot org
2009-10-04 8:06 ` ubizjak at gmail dot com
2009-10-04 8:16 ` ubizjak at gmail dot com
2009-10-10 20:55 ` danglin at gcc dot gnu dot org
2009-10-19 23:52 ` pinskia at gcc dot gnu dot org
2010-04-23 15:51 ` 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=bug-41159-4-9ZdoDvUs0h@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).