public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/46037] --enable-stage1-languages=c,lto --enable-languages=c,lto --with-build-config=bootstrap-lto fails on darwin
Date: Mon, 10 Jan 2011 22:47:00 -0000 [thread overview]
Message-ID: <bug-46037-4-BJQ1sJBxot@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46037-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46037
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.01.10 22:27:07
CC| |hubicka at gcc dot gnu.org,
| |joseph at codesourcery dot
| |com
Ever Confirmed|0 |1
--- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> 2011-01-10 22:27:07 UTC ---
Well, so the problem is:
static bool
ix86_valid_target_attribute_p (tree fndecl,
tree ARG_UNUSED (name),
tree args,
int ARG_UNUSED (flags))
{
...
new_optimize = build_optimization_node ();
...
if (old_optimize != new_optimize)
DECL_FUNCTION_SPECIFIC_OPTIMIZATION (fndecl) = new_optimize;
for some reason the optimization flags are believed to not match despite the
fact only target attribute is used. The difference is:
- <optimization_node 0x143209100
+ <optimization_node 0x100fda500
align_functions (0x10)
align_jumps (0x10)
align_labels (0x1)
@@ -95,5 +96,6 @@
flag_unwind_tables (0x1)
flag_var_tracking (0x1)
flag_var_tracking_assignments (0x1)
+ flag_var_tracking_uninit (0x1)
flag_vect_cost_model (0x1)
>
so it seems that re-running process_options on darwin somehow leads to this
change. Adding Joseph to CC.
Still streaming of optimization attribute is thing we should do.
next prev parent reply other threads:[~2011-01-10 22:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 14:36 [Bug bootstrap/46037] New: " howarth at nitro dot med.uc.edu
2010-10-16 1:24 ` [Bug bootstrap/46037] " howarth at nitro dot med.uc.edu
2010-10-16 9:46 ` rguenth at gcc dot gnu.org
2010-10-16 13:41 ` howarth at nitro dot med.uc.edu
2011-01-10 15:47 ` davek at gcc dot gnu.org
2011-01-10 15:47 ` Jan Hubicka
2011-01-10 15:52 ` hubicka at ucw dot cz
2011-01-10 22:47 ` hubicka at gcc dot gnu.org [this message]
2011-01-10 22:52 ` joseph at codesourcery dot com
2011-01-11 0:36 ` hubicka at gcc dot gnu.org
2011-01-11 0:45 ` hubicka at gcc dot gnu.org
2011-01-11 0:46 ` hubicka at gcc dot gnu.org
2011-01-11 5:20 ` howarth at nitro dot med.uc.edu
2011-01-11 6:55 ` howarth at nitro dot med.uc.edu
2011-01-11 7:02 ` howarth at nitro dot med.uc.edu
2011-01-11 10:09 ` hubicka at ucw dot cz
2011-01-11 14:03 ` howarth at nitro dot med.uc.edu
2011-01-11 14:08 ` Jan Hubicka
2011-01-11 14:09 ` hubicka at ucw dot cz
2011-01-11 15:29 ` howarth at nitro dot med.uc.edu
2011-01-11 15:30 ` howarth at nitro dot med.uc.edu
2011-01-11 16:34 ` howarth at nitro dot med.uc.edu
2011-01-11 17:02 ` Jan Hubicka
2011-01-11 17:03 ` hubicka at ucw dot cz
2011-01-11 18:46 ` howarth at nitro dot med.uc.edu
2011-01-11 21:20 ` [Bug target/46037] " howarth at nitro dot med.uc.edu
2011-01-12 3:29 ` mikestump at comcast dot net
2011-01-12 5:03 ` howarth at nitro dot med.uc.edu
2011-01-12 15:02 ` howarth at nitro dot med.uc.edu
2011-01-14 15:44 ` rguenth at gcc dot gnu.org
2011-01-14 16:36 ` howarth at nitro dot med.uc.edu
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-46037-4-BJQ1sJBxot@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).