public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth.at.gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/65733] gcc 4.9.2 suffers bootstrap comparison failures with clang 3.5.1 and later.
Date: Fri, 10 Apr 2015 23:46:00 -0000	[thread overview]
Message-ID: <bug-65733-4-3Tgxwv9Rpe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65733-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65733

--- Comment #3 from Jack Howarth <howarth.at.gcc at gmail dot com> ---
As Iain pointed out to me, the gcc configure output under the more recent clang
compilers isn't setting BUILD_CONFIG. Oddly gcc trunk also doesn't set
BUILD_CONFIG in the configure output under the more recent clang compilers but
the bootstrap comparison failure isn't seen. For gcc 4.9 and gcc-4_9-branch,
--with-build-config=bootstrap-debug  has to be explicitly passed to configure
to suppress the bootstrap comparison failures under the more recent clang
compilers.


  parent reply	other threads:[~2015-04-10 23:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 18:39 [Bug bootstrap/65733] New: " howarth.at.gcc at gmail dot com
2015-04-10 18:44 ` [Bug bootstrap/65733] " howarth.at.gcc at gmail dot com
2015-04-10 20:42 ` howarth.at.gcc at gmail dot com
2015-04-10 23:46 ` howarth.at.gcc at gmail dot com [this message]
2015-04-11  0:46 ` howarth.at.gcc at gmail dot com
2015-04-11  0:52 ` howarth.at.gcc at gmail dot com
2015-04-11  0:54 ` howarth.at.gcc at gmail dot com
2015-04-11  1:49 ` howarth.at.gcc at gmail dot com
2015-04-11  9:03 ` iains at gcc dot gnu.org
2015-04-11 12:34 ` howarth.at.gcc at gmail dot com
2015-04-11 14:17 ` howarth.at.gcc at gmail dot com
2015-04-11 17:12 ` howarth.at.gcc at gmail dot com

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-65733-4-3Tgxwv9Rpe@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).