public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ohaiziejohwahkeezuoz at xff dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/99898] New: Possible LTO object incompatibility on gcc-10 branch Date: Sat, 03 Apr 2021 16:20:20 +0000 [thread overview] Message-ID: <bug-99898-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99898 Bug ID: 99898 Summary: Possible LTO object incompatibility on gcc-10 branch Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: ohaiziejohwahkeezuoz at xff dot cz CC: marxin at gcc dot gnu.org Target Milestone: --- I'm trying gcc (releases/gcc-10 branch with the last commit Fri Oct 23 10:11:41 2020 +0200 - Fix up plugin header install) And I'm seeing an ICE cross-compiling glib library when linking with i686-linux-musl-gcc -o gio/gresource gio/gresource.p/gresource-tool.c.o -L/workspace/megous.com/apps-c/static-deps/output/i686/sys/usr/lib -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -static -Wl,--start-group gio/libgio-2.0.a glib/libglib-2.0.a gobject/libgobject-2.0.a gmodule/libgmodule-2.0.a /workspace/megous.com/apps-c/static-deps/output/i686/sys/usr/lib/libz.a /workspace/megous.com/apps-c/static-deps/output/i686/sys/usr/lib/libmount.a /workspace/megous.com/apps-c/static-deps/output/i686/sys/usr/lib/libblkid.a -pthread -liconv -lm /workspace/megous.com/apps-c/static-deps/output/i686/sys/usr/lib/libffi.a -Wl,--end-group lto1: internal compiler error: in lto_read_decls, at lto/lto-common.c:1956 Please submit a full bug report, with preprocessed source if appropriate. I'm compiling with fat LTO objects, and this only happens when mixing LTO object files compiled with previous version of gcc on the tip of gcc-10 branch. (and only with i686 target so far) Sorry I don't have precise version of the previous compiler, but it was probably something close to 10.2 judging by the dates on the object files. Recompiling all dependencies with the same version of the compiler doesn't lead to this ICE. Maybe LTO version needs a bump prior to 10.3 release?
next reply other threads:[~2021-04-03 16:20 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-03 16:20 ohaiziejohwahkeezuoz at xff dot cz [this message] 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 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@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: linkBe 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).