public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin 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: Wed, 28 Dec 2022 09:39:26 +0000	[thread overview]
Message-ID: <bug-107597-4-3R2821DGBs@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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|marxin at gcc dot gnu.org          |unassigned at gcc dot gnu.org
             Status|ASSIGNED                    |NEW

--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
> So this is kind of feature.   How the ODR violations are detected?
> I wonder if keeping weak flag disturbs something.

ASAN emits so-called ODR indicators for all global symbols that survive the
following check: asan_needs_odr_indicator_p (tree decl)
in asan.cc:3216

And that's we see 2 of them:

marxin@marxinbox:~/Programming/testcases/PR107597> nm libTest1.so | grep odr
00000000000040c0 B __odr_asan._ZN12NonTemplated1xE
marxin@marxinbox:~/Programming/testcases/PR107597> nm libTest2.so | grep odr
00000000000040c0 B __odr_asan._ZN12NonTemplated1xE

which eventually ends up with the run-time error.

  parent reply	other threads:[~2022-12-28  9:39 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 ` [Bug c++/107597] " rguenth at gcc dot gnu.org
2022-11-11 17:42 ` 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 [this message]
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-3R2821DGBs@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).