public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/99898] Possible LTO object incompatibility on gcc-10 branch
Date: Tue, 06 Apr 2021 10:03:16 +0000 [thread overview]
Message-ID: <bug-99898-4-cYjgoqugR0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99898-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99898
--- Comment #5 from Jan Hubicka <hubicka at ucw dot cz> ---
> The LTO minor saw a bump around Sep 10 last year already so the object files
> must be younger or LTO should complain.
>
> I'm not aware of any specific change where we forgot the bumping but there were
> a lot of changes and since we did already bump bumping again shouldn't cause
> any harm. Still I'd like to be sure we're not seeing a genuine streaming bug
> here.
I only reacall backporting the streaming fixes early in gcc10 timeframe
(August) that was reason for the September bump.
Didn't we backport some new command line options/params breaking
streaming of optimization nodes as usual?
honza
next prev parent reply other threads:[~2021-04-06 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 16:20 [Bug lto/99898] New: " ohaiziejohwahkeezuoz at xff dot cz
2021-04-03 17:34 ` [Bug lto/99898] " ohaiziejohwahkeezuoz at xff dot cz
2021-04-04 5:10 ` pinskia at gcc dot gnu.org
2021-04-06 6:20 ` marxin at gcc dot gnu.org
2021-04-06 6:59 ` rguenth at gcc dot gnu.org
2021-04-06 10:03 ` hubicka at ucw dot cz [this message]
2021-04-06 10:07 ` hubicka at ucw dot cz
2021-04-06 10:08 ` jakub at gcc dot gnu.org
2021-04-06 10:11 ` Jan Hubicka
2021-04-06 10:11 ` hubicka at ucw dot cz
2021-04-06 10:26 ` jakub at gcc dot gnu.org
2021-04-06 11:32 ` hubicka at ucw dot cz
2021-04-08 8:58 ` cvs-commit at gcc dot gnu.org
2021-04-08 8:58 ` 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-99898-4-cYjgoqugR0@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).