public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113341] Using GCC as the bootstrap compiler breaks LLVM on 32-bit PowerPC
Date: Sat, 15 Jun 2024 13:38:03 +0000 [thread overview]
Message-ID: <bug-113341-4-kHvCgbj7RI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113341-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at gcc dot gnu.org
--- Comment #12 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to John Paul Adrian Glaubitz from comment #11)
> (In reply to John Paul Adrian Glaubitz from comment #10)
> > (In reply to Kewen Lin from comment #9)
> > > Since it's a breakage during stage2, it's concluded that some built stage1
> > > stuffs behave unexpectedly. You probably can try to run regression testing
> > > just with stage1 compiler to see if there is any regression exposed.
> > >
> > > If without any luck, then you probably have to isolate into one or several
> > > object files, since you have "objects" for "good" and "bad" stage1 compiler,
> > > you can be able to isolate some in between further. Once you get some
> > > isolated, you can probably get some hints it's a bug in LLVM source or gcc.
> >
> > Thanks. This sounds like a good idea. I will try to identify the object
> > files that differ.
>
> First result of the comparison is that Clang and GCC are building with
> different flags:
>
> Clang-only flags: -Werror=unguarded-availability-new
> -Wc++98-compat-extra-semi -Wcovered-switch-default -Wnon-virtual-dtor
> -Wstring-conversion -Wmisleading-indentation
>
> GCC-only flags: -fno-lifetime-dse -Wno-missing-field-initializers
> -Wno-maybe-uninitialized -Wno-nonnull -Wno-class-memaccess
> -Wno-redundant-move -Wno-pessimizing-move -Wno-comment
> -Wno-misleading-indentation
>
> I'll upload the build results later to my cloud space if anyone wants to
> help debug as the diff between the two build folders is rather big.
-Wxxx shouldn't have an effect on code generation. -fno-lifetime-dse is quite
intentional, see PR106943.
next prev parent reply other threads:[~2024-06-15 13:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 22:07 [Bug target/113341] New: " glaubitz at physik dot fu-berlin.de
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
2024-06-14 20:29 ` glaubitz at physik dot fu-berlin.de
2024-06-15 12:46 ` glaubitz at physik dot fu-berlin.de
2024-06-15 13:38 ` xry111 at gcc dot gnu.org [this message]
2024-06-15 13:44 ` glaubitz at physik dot fu-berlin.de
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-kHvCgbj7RI@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).