public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104631] Visibility of static member s yields duplicate symbols.
Date: Fri, 22 Apr 2022 14:58:29 +0000	[thread overview]
Message-ID: <bug-104631-4-bCesSxsUY3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104631-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104631

Alexander Monakov <amonakov at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amonakov at gcc dot gnu.org

--- Comment #3 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Note that what matters is not the type of the member, but whether template
parameters have hidden visibility, as the following example demonstrates:

struct S {
};

template<class T>
struct TS {
        __attribute__((visibility("default")))
        static int i;
        __attribute__((visibility("default")))
        static S s;
};

template<class T>
int TS<T>::i{};

template<class T>
S TS<T>::s{};

template struct TS<int>;
template struct TS<S>;

      parent reply	other threads:[~2022-04-22 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22  8:12 [Bug c++/104631] New: " max.sagebaum at scicomp dot uni-kl.de
2022-02-22  8:46 ` [Bug c++/104631] " pinskia at gcc dot gnu.org
2022-02-22  9:10 ` max.sagebaum at scicomp dot uni-kl.de
2022-04-22 14:58 ` amonakov at gcc dot gnu.org [this message]

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-104631-4-bCesSxsUY3@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).