public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/49299] ICE in gimple_ic on profile feedback build
Date: Mon, 06 Jun 2011 10:57:00 -0000 [thread overview]
Message-ID: <bug-49299-4-0RlqjxWQNS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49299-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49299
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org
|gnu.org |
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-06-06 10:56:55 UTC ---
Created attachment 24447
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24447
gcc46-pr49299.patch
Untested fix. Turning of a normal indirect call into an optionally direct
noreturn call seems to work and worked before too.
Anyway, if you prefer to just give up in gimple_ic_transform instead, like
/* Don't optimize noreturn calls, they should be cold. */
if (gimple_call_flags (stmt) & ECF_NORETURN)
return false;
I can test that instead.
next prev parent reply other threads:[~2011-06-06 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 9:12 [Bug gcov-profile/49299] New: " andi-gcc at firstfloor dot org
2011-06-06 9:12 ` [Bug gcov-profile/49299] " andi-gcc at firstfloor dot org
2011-06-06 9:41 ` jakub at gcc dot gnu.org
2011-06-06 9:42 ` jakub at gcc dot gnu.org
2011-06-06 9:51 ` andi-gcc at firstfloor dot org
2011-06-06 10:30 ` rguenth at gcc dot gnu.org
2011-06-06 10:57 ` jakub at gcc dot gnu.org [this message]
2011-06-07 9:49 ` jakub at gcc dot gnu.org
2011-06-07 9:54 ` jakub at gcc dot gnu.org
2011-06-07 9:55 ` 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-49299-4-0RlqjxWQNS@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).