From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7027F39B5D1B; Thu, 29 Jul 2021 15:40:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7027F39B5D1B From: "iains at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2021 15:40:07 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100340 --- Comment #11 from Iain Sandoe --- (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 t= his > for now?=20 >=20 > 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 d= oes > 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=3Dfalse` (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 s= ee > if 11.2 fixes them!) please CC me on Darwin/macOS bugs -- too many mailing lists ;-) I miss bugs sometimes.=