public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uweigand at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/41771] Bootstrap with Sun Studio 12.1 fails Date: Thu, 05 Nov 2009 13:31:00 -0000 [thread overview] Message-ID: <20091105133124.32432.qmail@sourceware.org> (raw) In-Reply-To: <bug-41771-279@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from uweigand at gcc dot gnu dot org 2009-11-05 13:31 ------- (In reply to comment #10) > If this is problematic, I guess an alternative might be to move the > HONOR_... macros from flags.h to real.h as well, and update all files > that use these macros to also include real.h. >From a quick review, this seems to be pretty straightforward -- all files using the HONOR_... macros already include real.h either directly or indirectly via its inclusion in rtl.h, with the single exception of tree-ssa-reassoc.c. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41771
next prev parent reply other threads:[~2009-11-05 13:31 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-20 19:15 [Bug bootstrap/41771] New: " ro at gcc dot gnu dot org 2009-10-20 19:17 ` [Bug bootstrap/41771] " ro at gcc dot gnu dot org 2009-10-21 1:49 ` ghazi at gcc dot gnu dot org 2009-10-21 10:54 ` ro at techfak dot uni-bielefeld dot de 2009-10-21 13:37 ` ro at techfak dot uni-bielefeld dot de 2009-10-21 19:51 ` ghazi at gcc dot gnu dot org 2009-10-22 17:09 ` ro at techfak dot uni-bielefeld dot de 2009-10-22 18:13 ` ghazi at gcc dot gnu dot org 2009-10-22 18:20 ` ro at techfak dot uni-bielefeld dot de 2009-11-05 2:55 ` ghazi at gcc dot gnu dot org 2009-11-05 13:18 ` uweigand at gcc dot gnu dot org 2009-11-05 13:31 ` uweigand at gcc dot gnu dot org [this message] 2009-11-29 16:34 ` ghazi at gcc dot gnu dot org 2009-12-11 17:55 ` ro at gcc dot gnu dot org 2009-12-11 18:38 ` ro at CeBiTec dot Uni-Bielefeld dot DE 2010-01-05 17:15 ` ro at gcc dot gnu dot org 2010-01-06 18:07 ` ro at gcc dot gnu dot 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=20091105133124.32432.qmail@sourceware.org \ --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: linkBe 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).