public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47598] -fgraphite-identity at -O2 breaks profiledbootstrap
Date: Thu, 03 Feb 2011 16:25:00 -0000 [thread overview]
Message-ID: <bug-47598-4-sOgo1spHYx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47598-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47598
--- Comment #5 from Jack Howarth <howarth at nitro dot med.uc.edu> 2011-02-03 16:25:02 UTC ---
(In reply to comment #4)
> Can you create a standalone testcase to show this -fgraphite-identity -O2 bug?
I think that will be rather difficult to achieve since the bug is occurring in
the -fprofile-use stage requiring the generated profiles. I can check that this
can also be observed on x86_64 linux though.
next prev parent reply other threads:[~2011-02-03 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 15:01 [Bug middle-end/47598] New: " howarth at nitro dot med.uc.edu
2011-02-03 15:06 ` [Bug middle-end/47598] " howarth at nitro dot med.uc.edu
2011-02-03 15:18 ` howarth at nitro dot med.uc.edu
2011-02-03 15:37 ` howarth at nitro dot med.uc.edu
2011-02-03 15:53 ` hjl.tools at gmail dot com
2011-02-03 16:25 ` howarth at nitro dot med.uc.edu [this message]
2011-02-03 23:54 ` howarth at nitro dot med.uc.edu
2015-10-09 16:28 ` spop 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-47598-4-sOgo1spHYx@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).