public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Wed, 27 Jan 2021 09:42:07 +0000 [thread overview]
Message-ID: <bug-85574-4-okhD5AggMZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #36 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Because I didn't try to invent a clever way to detect which ones will
> actually exist (but I know lto1 will). Sure some extra-compare-if-exists
> could be invented. If there's no way to compare binaries on windows
> then there's maybe a way to conditionalize the extra-compare setting
> in the makefile fragment.
There is one, see above. And it looks like contrib/compare-lto should be
rewritten from scratch, it takes a lot of time on Windows for nothing IIUC.
next prev parent reply other threads:[~2021-01-27 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-85574-4@http.gcc.gnu.org/bugzilla/>
2021-01-26 15:45 ` ebotcazou at gcc dot gnu.org
2021-01-26 19:35 ` ebotcazou at gcc dot gnu.org
2021-01-27 9:04 ` rguenth at gcc dot gnu.org
2021-01-27 9:42 ` ebotcazou at gcc dot gnu.org [this message]
2021-01-27 10:54 ` rguenther at suse dot de
2021-01-27 20:18 ` ebotcazou at gcc dot gnu.org
2021-01-28 10:34 ` cvs-commit at gcc dot gnu.org
2021-01-28 10:35 ` cvs-commit at gcc dot gnu.org
2021-01-28 10:40 ` cvs-commit 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-85574-4-okhD5AggMZ@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).