public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113341] New: Using GCC as the bootstrap compiler breaks LLVM on 32-bit PowerPC
Date: Thu, 11 Jan 2024 22:07:12 +0000 [thread overview]
Message-ID: <bug-113341-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
Bug ID: 113341
Summary: Using GCC as the bootstrap compiler breaks LLVM on
32-bit PowerPC
Product: gcc
Version: 13.2.1
URL: https://github.com/llvm/llvm-project/issues/72279
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: glaubitz at physik dot fu-berlin.de
CC: jrtc27 at jrtc27 dot com, segher at gcc dot gnu.org,
sjames at gcc dot gnu.org
Target Milestone: ---
Using GCC on 32-bit PowerPC as the bootstrap compiler to build LLVM leads to
clang crashing during stage 2 with a backtrace. This does not happen when LLVM
is used as the bootstrap compiler.
The backtrace that clang generates can be found in the LLVM bug report [1].
The problem was observed with LLVM 17, so I initially suspected a regression in
LLVM. I was able to bisect issue which lead to the following commit in LLVM:
bc73ef0031b50f7443615fef614fb4ecaaa4bd11 is the first bad commit
commit bc73ef0031b50f7443615fef614fb4ecaaa4bd11
Author: Richard Smith <richard@metafoo.co.uk>
Date: Thu Mar 30 14:21:31 2023 -0700
PR60985: Fix merging of lambda closure types across modules.
However, since the problem does not show when using LLVM as the bootstrap
compiler instead of GCC, I'm suspecting that GCC is miscompiling the code.
> [1] https://github.com/llvm/llvm-project/issues/72279
next reply other threads:[~2024-01-11 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 22:07 glaubitz at physik dot fu-berlin.de [this message]
2024-01-11 22:13 ` [Bug target/113341] " pinskia at gcc dot gnu.org
2024-01-11 22:14 ` segher at gcc dot gnu.org
2024-01-11 22:18 ` glaubitz at physik dot fu-berlin.de
2024-01-11 22:18 ` pinskia at gcc dot gnu.org
2024-01-11 22:28 ` segher at gcc dot gnu.org
2024-01-11 22:32 ` pinskia at gcc dot gnu.org
2024-01-11 22:38 ` pinskia at gcc dot gnu.org
2024-01-11 22:42 ` jrtc27 at jrtc27 dot com
2024-01-12 8:04 ` linkw 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-113341-4@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).