public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100340] Bootstrap fails with Clang 12.0.5 (XCode 12.5)
Date: Thu, 29 Jul 2021 15:40:07 +0000	[thread overview]
Message-ID: <bug-100340-4-xTM2wJqFZn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100340-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Matt Thompson from comment #10)
> Query from someone who I believe just encountered this trying to build 11.2
> on macOS 11.5.1 with XCode 12.5: What is the best method to work around this
> for now? 
> 
> 1. Update to XCode 12.5.1 (which apparently exists, but I don't know if it
> has the fixes?)

not yet checked - but if someone has time I'd like to know ;)

> 2. Pass in `--without-build-config` to configure (which is how Homebrew does
> it)

the disadvantage of that is that it skips the compare objects stage (because
that is what fails) .. but it works, indeed.

> 3. Iain's last suggestion about `-mllvm -x86-pad-for-align=false` (I'm not
> sure where to put that)

We will need configure to detect version(s) of the assembler that fail and to
apply this to the 'as' lines where needed - I didn't get to this because it's
far from a 5mins job and:

a) was hoping for a fix [does anyone know if 12.5.1 fixes?]

b) it was easier for me to revert to using command-line-tools 12.4 for X86 (the
bug doesn't fire for my experimental work on arm64, so I can use 12.5 there).

... having said that, if we don't see a fix soon and there end up being
un-fixable configurations (e.g. versions which don't support a fixed Xcode,
then we'll need to do the configury magic).

> The easiest for me to try was #2 and it seems to work, but I don't know if
> that has side-effects for the built compiler.

as noted above - no side effects on the compiler, but a reduction in the
testing of the build.

> (Of course, our software currently has some issues with GCC 11.1 that I
> think are still open here on Bugzilla (like #100651), but I thought I'd see
> if 11.2 fixes them!)

please CC me on Darwin/macOS bugs -- too many mailing lists ;-) I miss bugs
sometimes.

  parent reply	other threads:[~2021-07-29 15:40 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 19:48 [Bug bootstrap/100340] New: " juergen.reuter at desy dot de
2021-04-29 19:49 ` [Bug bootstrap/100340] " juergen.reuter at desy dot de
2021-04-29 21:17 ` juergen.reuter at desy dot de
2021-04-29 23:38 ` dominiq at lps dot ens.fr
2021-04-30  5:09 ` juergen.reuter at desy dot de
2021-04-30  6:47 ` rguenth at gcc dot gnu.org
2021-04-30  6:55 ` iains at gcc dot gnu.org
2021-04-30  8:38 ` [Bug target/100340] " iains at gcc dot gnu.org
2021-04-30 12:09 ` juergen.reuter at desy dot de
2021-05-25 16:25 ` iains at gcc dot gnu.org
2021-07-29 14:49 ` matthew.thompson at nasa dot gov
2021-07-29 15:40 ` iains at gcc dot gnu.org [this message]
2021-07-29 20:31 ` juergen.reuter at desy dot de
2021-07-30 15:53 ` jonesc at hep dot phy.cam.ac.uk
2021-07-30 15:55 ` jonesc at hep dot phy.cam.ac.uk
2021-07-30 16:23 ` iains at gcc dot gnu.org
2021-08-02 13:36 ` matthew.thompson at nasa dot gov
2021-08-02 13:39 ` jonesc at hep dot phy.cam.ac.uk
2021-08-02 13:42 ` jonesc at hep dot phy.cam.ac.uk
2021-08-02 13:43 ` matthew.thompson at nasa dot gov
2021-08-02 14:17 ` iains at gcc dot gnu.org
2021-08-04 15:45 ` iains at gcc dot gnu.org
2021-08-17 18:39 ` cvs-commit at gcc dot gnu.org
2021-08-17 18:42 ` iains at gcc dot gnu.org
2021-09-27 17:10 ` matthew.thompson at nasa dot gov
2021-09-27 17:59 ` iains at gcc dot gnu.org
2021-10-02 22:51 ` fink at snaggledworks dot com
2021-10-13 19:59 ` cvs-commit at gcc dot gnu.org
2021-11-29 19:00 ` egallager at gcc dot gnu.org
2022-04-19 10:51 ` kirill at korins dot ky
2022-04-19 11:08 ` iains at gcc dot gnu.org
2022-04-19 11:45 ` kirill at korins dot ky
2022-05-27  9:04 ` rguenth at gcc dot gnu.org
2022-05-27  9:29 ` iains at gcc dot gnu.org
2022-05-29 19:03 ` cvs-commit at gcc dot gnu.org
2022-05-29 19:21 ` iains at gcc dot gnu.org
2022-07-27 17:12 ` egallager at gcc dot gnu.org
2022-07-27 18:18 ` iains 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-100340-4-xTM2wJqFZn@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).