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 c++/107597] LTO causes static inline variables to get a non-uniqued global symbol Date: Thu, 10 Nov 2022 07:31:02 +0000 [thread overview] Message-ID: <bug-107597-4-G9pO046mG6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107597-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107597 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amodra at gcc dot gnu.org, | |hubicka at gcc dot gnu.org, | |jason at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2022-11-10 Keywords| |lto, wrong-code Status|UNCONFIRMED |NEW --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- 1 libFoo.so-t.o 2 192 c3d22ca2af7ab12c PREVAILING_DEF_IRONLY_EXP main 197 c3d22ca2af7ab12c PREVAILING_DEF_IRONLY_EXP _ZN12NonTemplated1xE confirmed (binutils 2.37). I think the above shows the linker doesn't properly communicate the uniqueness but we might be able to recover from the bits we have in the streamed IL?
next prev parent reply other threads:[~2022-11-10 7:31 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-09 19:09 [Bug c++/107597] New: " cfsteefel at arista dot com 2022-11-10 7:31 ` rguenth at gcc dot gnu.org [this message] 2022-11-11 17:42 ` [Bug c++/107597] " hubicka at ucw dot cz 2022-11-14 17:38 ` cfsteefel at arista dot com 2022-11-21 10:12 ` marxin at gcc dot gnu.org 2022-12-28 9:37 ` marxin at gcc dot gnu.org 2022-12-28 9:39 ` marxin at gcc dot gnu.org 2023-01-04 17:28 ` hubicka 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-107597-4-G9pO046mG6@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).