public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luto at mit dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55347] New: Specialized member of class template prevents visibility setting Date: Thu, 15 Nov 2012 20:57:00 -0000 [thread overview] Message-ID: <bug-55347-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55347 Bug #: 55347 Summary: Specialized member of class template prevents visibility setting Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: luto@mit.edu Compiling this code: --- cut here --- template<typename T> class A { void func() {} }; //#pragma GCC visibility push(default) -- no effect template<> void A<int>::func() {} // This causes a problem template class __attribute__((visibility("default"))) A<int>; //#pragma GCC visibility pop --- cut here --- results in: template_visibility.cc:10:55: warning: type attributes ignored after type is already defined [-Wattributes] The emitted code ends up hidden. This is a minor issue in C++98 (I'm not sure why you'd want to do this), but it's an actual problem in C++11: extern templates behave the same way. I think that gcc's behavior is consistent, but there should be a way to override the visibility of a particular class template specialization *without instantiating/defining it*, then specialize a member, then instantiate the template.
reply other threads:[~2012-11-15 20:57 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-55347-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).