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 c/50506] gcc fails at assembly with -O1 while inlining is forced
Date: Sun, 25 Sep 2011 17:20:00 -0000 [thread overview]
Message-ID: <bug-50506-4-sh7KxY8rmf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50506-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50506
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WONTFIX
--- Comment #11 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-09-25 17:16:16 UTC ---
(In reply to comment #9)
> What I'm trying to say is that gcc should either:
> - accept the code even with -fno-ipa-cp
> - reject the code even with -fipa-cp
> - print better diagnostics, if -fipa-cp should be the magic switch to make the
> code work
only -fipa-cp makes us see that the indirect call resolves to an always-inline
function. We could issue an error whenever the out-of-line body of an
always-inline function cannot be removed after optimization, but that would
upset even more people.
next prev parent reply other threads:[~2011-09-25 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 13:08 [Bug c/50506] New: " galtgendo at o2 dot pl
2011-09-24 13:18 ` [Bug c/50506] " galtgendo at o2 dot pl
2011-09-24 13:18 ` galtgendo at o2 dot pl
2011-09-24 13:46 ` galtgendo at o2 dot pl
2011-09-24 14:18 ` galtgendo at o2 dot pl
2011-09-24 16:05 ` pinskia at gcc dot gnu.org
2011-09-24 16:24 ` galtgendo at o2 dot pl
2011-09-25 12:27 ` rguenth at gcc dot gnu.org
2011-09-25 13:22 ` galtgendo at o2 dot pl
2011-09-25 13:58 ` galtgendo at o2 dot pl
2011-09-25 14:12 ` galtgendo at o2 dot pl
2011-09-25 17:20 ` rguenth at gcc dot gnu.org [this message]
2011-09-25 18:10 ` galtgendo at o2 dot pl
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-50506-4-sh7KxY8rmf@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).