public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/50483] lto turns visibility from HIDDEN to DEFAULT Date: Sat, 01 Jan 2022 23:20:46 +0000 [thread overview] Message-ID: <bug-50483-4-QOvpZPhwHI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50483-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50483 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So what is happening is bar is being coming localized to the newly produced assembly file which is the same as being hidden really. If we do: void bar() __attribute((visibility( "hidden" ), externally_visible)); The new assembly file in both cases produces: .globl _Z3barv .hidden _Z3barv Without the externally_visible, the function does not have a .globl to it. This is also why in both with and without -flto dynsym does not have the symbol there. There is no bug to be fixed, LTO is doing the localizing rather than the linker doing it.
next prev parent reply other threads:[~2022-01-01 23:20 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-22 11:26 [Bug lto/50483] New: " vincenzo.innocente at cern dot ch 2011-09-25 12:04 ` [Bug lto/50483] " rguenth at gcc dot gnu.org 2022-01-01 23:20 ` pinskia at gcc dot gnu.org [this message] 2022-01-01 23:28 ` pinskia 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-50483-4-QOvpZPhwHI@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).