public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/101383] GCC 11 Reproducibility Issue
Date: Fri, 09 Jul 2021 08:35:03 +0000 [thread overview]
Message-ID: <bug-101383-4-nX2N5gWP1Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101383-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101383
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
The difference you show lists temporary assembler filenames - I don't see
any of those in a local bootstrap (but I just have trunk lying around).
cc1-checksum is copied to make the checksum the same on all stages.
The flags are different between stage2 and stage3 to increase coverage
of the same-code check (once with debug, once without) and to make
the build faster (do less checking using the very slow stage1 compiler).
The cc1-checksum is a source of difference between builds, at SUSE we carry
a local patch to null that and instead use the linker build-id as checksum
for PCH purposes.
next prev parent reply other threads:[~2021-07-09 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 7:42 [Bug other/101383] New: " toolybird at tuta dot io
2021-07-09 8:35 ` rguenth at gcc dot gnu.org [this message]
2021-07-09 8:53 ` [Bug other/101383] " rguenth at gcc dot gnu.org
2021-07-09 8:58 ` [Bug debug/101383] " rguenth at gcc dot gnu.org
2021-07-09 9:08 ` [Bug driver/101383] " rguenth at gcc dot gnu.org
2021-07-09 9:12 ` rguenth at gcc dot gnu.org
2021-07-09 21:04 ` toolybird at tuta dot io
2021-07-15 5:56 ` cvs-commit at gcc dot gnu.org
2021-07-15 6:34 ` cvs-commit at gcc dot gnu.org
2021-07-15 6:35 ` rguenth 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-101383-4-nX2N5gWP1Q@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).