public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhykzhykzhyk at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66944] New: static thread_local member in class template may cause compilation to fail
Date: Mon, 20 Jul 2015 15:23:00 -0000	[thread overview]
Message-ID: <bug-66944-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 66944
           Summary: static thread_local member in class template may cause
                    compilation to fail
           Product: gcc
           Version: 5.2.0
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zhykzhykzhyk at gmail dot com
  Target Milestone: ---

Affect Versions: 4.9.3, 5.1.0, 5.2.0

Expected behavior:
  compiles correctly (like clang does)

Compiler output:
bug.cc:14:34: error: redefinition of 'bool __tls_guard'
 thread_local std::vector<void *> A<T>::v;
                                  ^
bug.cc:14:34: note: 'bool __tls_guard' previously declared here
bug.cc:14: confused by earlier errors, bailing out

== code ==
struct Heavy { Heavy(){} };

template <typename T>
struct A {
  virtual void foo() { v; }
  static thread_local Heavy v;
};

template <typename T>
thread_local Heavy A<T>::v;

struct E {};
struct F {};

int main() {
  A<E> foo;
  A<F> bar;
  bar.v;
}
==========


                 reply	other threads:[~2015-07-20 15:23 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-66944-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: 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).