public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106023] New: Would like to control the ELF visibility of template explicit instantiations Date: Sat, 18 Jun 2022 15:16:16 +0000 [thread overview] Message-ID: <bug-106023-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106023 Bug ID: 106023 Summary: Would like to control the ELF visibility of template explicit instantiations Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: thiago at kde dot org Target Milestone: --- Given a template like: template <typename T> struct __attribute__((visibility("hidden"))) S { static constexpr int n = 0; }; I would like to mark an explicit instantiation (not a specialisation!) with a different visibility: template struct __attribute__((visibility("default"))) S<int>; template __attribute__((visibility("default"))) const int S<unsigned>::n; Either solution would help me, but the first would be preferable. Both would be best. Clang does support both forms properly. Visual Studio supports the former only. See https://gcc.godbolt.org/z/T7sdzTnbG and note how GCC adds ".hidden" to the two "::n" symbols and Clang doesn't, while Clang properly refers to those symbols using @GOTPCREL and GCC doesn't. The MVSC example uses dllimport only to highlight the difference; it wouldn't be written like this in real code. Please ensure "protected" visibility also works. See https://gcc.godbolt.org/z/o3W4x5YsG
next reply other threads:[~2022-06-18 15:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-18 15:16 thiago at kde dot org [this message] 2022-06-18 20:06 ` [Bug c++/106023] " pinskia at gcc dot gnu.org 2022-06-19 16:04 ` thiago at kde dot 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-106023-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).