public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager 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: Mon, 29 Nov 2021 19:00:28 +0000 [thread overview]
Message-ID: <bug-100340-4-dZZtaiTbDe@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 #28 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to CVS Commits from comment #27)
> The releases/gcc-11 branch has been updated by Iain D Sandoe
> <iains@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:8b333df9484c1697f3a80530a47aa90b1859e970
>
> commit r11-9147-g8b333df9484c1697f3a80530a47aa90b1859e970
> Author: Iain Sandoe <iain@sandoe.co.uk>
> Date: Sat Jul 31 16:29:03 2021 +0100
>
> Darwin, X86, config: Adjust 'as' command lines [PR100340].
>
> Versions of the assembler using clang from XCode 12.5/12.5.1
> have a bug which produces different code layout between debug and
> non-debug input, leading to a compare fail for default configure
> parameters.
>
> This is a workaround fix to disable the optimisation that is
> responsible for the bug.
>
> Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
>
> PR target/100340 - Bootstrap fails with Clang 12.0.5 (XCode 12.5)
>
> PR target/100340
>
> gcc/ChangeLog:
>
> * config.in: Regenerate.
> * config/i386/darwin.h (EXTRA_ASM_OPTS): New
> (ASM_SPEC): Pass options to disable branch shortening where
> needed.
> * configure: Regenerate.
> * configure.ac: Detect versions of 'as' that support the
> optimisation which has the bug.
>
> (cherry picked from commit 743b8dd6fd757e997eb060d70fd4ae8e04fb56cd)
Did this fix it? (asking due to downstream issue
https://trac.macports.org/ticket/63312 in MacPorts, btw)
next prev parent reply other threads:[~2021-11-29 19:00 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
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 [this message]
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-dZZtaiTbDe@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).