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/56061] [4.8 Regression] ICE in lto1 (in inline_call, at ipa-inline-transform.c:267)
Date: Wed, 30 Jan 2013 11:21:00 -0000 [thread overview]
Message-ID: <bug-56061-4-y0EBWGYsNS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56061-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56061
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-30 11:21:11 UTC ---
(In reply to comment #2)
> (In reply to comment #1)
>
> > I don't think we necessarily want to support this fully...
>
> Are such bug reports useful, or it's just a nuisance to you, gcc devs? :)
They are useful. It should be technically possible to support -O1 vs. -O0,
and if not, we have means to forcefully enable -O1 at link-time (which we
should do then).
next prev parent reply other threads:[~2013-01-30 11:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 6:30 [Bug lto/56061] New: " d.g.gorbachev at gmail dot com
2013-01-23 16:28 ` [Bug lto/56061] " rguenth at gcc dot gnu.org
2013-01-28 14:35 ` rguenth at gcc dot gnu.org
2013-01-30 10:54 ` d.g.gorbachev at gmail dot com
2013-01-30 11:21 ` rguenth at gcc dot gnu.org [this message]
2013-01-30 11:21 ` manu at gcc dot gnu.org
2013-01-30 11:26 ` rguenth at gcc dot gnu.org
2013-01-30 11:29 ` manu at gcc dot gnu.org
2013-01-30 13:40 ` d.g.gorbachev at gmail dot com
2013-01-30 17:17 ` hubicka at ucw dot cz
2013-02-26 15:17 ` rguenth at gcc dot gnu.org
2013-03-22 14:43 ` [Bug lto/56061] [4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 10:58 ` jakub at gcc dot gnu.org
2013-10-16 9:48 ` jakub at gcc dot gnu.org
2014-05-22 9:02 ` [Bug lto/56061] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:34 ` [Bug lto/56061] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-01-29 7:20 ` [Bug lto/56061] [4.8/4.9 " hubicka at gcc dot gnu.org
2015-06-23 8:15 ` rguenth at gcc dot gnu.org
2015-06-26 20:04 ` [Bug lto/56061] [4.9 " jakub at gcc dot gnu.org
2015-06-26 20:33 ` jakub 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-56061-4-y0EBWGYsNS@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).