public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ak at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56580] Internal compiler error when trying to compile a sequence of NOPs inside a loop
Date: Wed, 08 Oct 2014 03:32:00 -0000 [thread overview]
Message-ID: <bug-56580-4-33auTnUCDk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56580-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56580
ak at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ak at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #5 from ak at gcc dot gnu.org ---
Fixed since some time in trunk with
2013-09-08 Andi Kleen <ak@linux.intel.com>
* tree-inline.c (estimate_num_insns): Limit asm cost to 1000.
prev parent reply other threads:[~2014-10-08 3:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 17:34 [Bug c/56580] New: " ahyangyi at gmail dot com
2013-03-09 17:37 ` [Bug c/56580] " ahyangyi at gmail dot com
2013-03-11 10:23 ` [Bug tree-optimization/56580] " rguenth at gcc dot gnu.org
2013-03-14 16:25 ` pinskia at gcc dot gnu.org
2013-03-20 12:06 ` rguenth at gcc dot gnu.org
2014-10-08 3:32 ` ak at gcc dot gnu.org [this message]
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-56580-4-33auTnUCDk@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).