public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47038] gcc.dg/pr46685.c FAILs on Solaris 10/SPARC
Date: Fri, 24 Dec 2010 16:07:00 -0000 [thread overview]
Message-ID: <bug-47038-4-zHmqZmqnyK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47038-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47038
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2010.12.24 16:07:24
Ever Confirmed|0 |1
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2010-12-24 16:07:24 UTC ---
> Hmmm... is this a dup of pr40483? Can someone confirm?
No, this looks unrelated. This has been introduced by:
2010-12-20 Iain Sandoe <iains@gcc.gnu.org>
Jan Hubicka <jh@suse.cz>
PR middle-end/46916
* opts.c (finish_options): Enable -freorder-functions
when -freorder-blocks-and-partition is active.
next prev parent reply other threads:[~2010-12-24 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 4:12 [Bug target/47038] New: " gseanmcg at gmail dot com
2010-12-22 16:27 ` [Bug target/47038] " gseanmcg at gmail dot com
2010-12-24 16:07 ` ebotcazou at gcc dot gnu.org [this message]
2010-12-24 16:09 ` ebotcazou at gcc dot gnu.org
2010-12-28 15:25 ` [Bug target/47038] [4.6 Regression] failure of gcc.dg/pr46685.c ebotcazou at gcc dot gnu.org
2010-12-30 21:31 ` ebotcazou at gcc dot gnu.org
2010-12-30 21:33 ` ebotcazou at gcc dot gnu.org
2011-01-03 12:07 ` ebotcazou 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-47038-4-zHmqZmqnyK@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).