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 c++/66360] thread_local variable needs copy constructor Date: Mon, 01 Jun 2015 13:30:00 -0000 [thread overview] Message-ID: <bug-66360-4-f3ABPjrTRX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66360-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66360 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This has nothing to do with thread_local. That is removing static thread_local still causes it to produce an error. Here is a more reduced testcase: template <typename T> struct wrapper final { T value; template <typename ...Args> wrapper(Args &&...args) : value(args...) { } }; struct non_copyable { non_copyable(const non_copyable &) = delete; non_copyable(); ~non_copyable(); }; template <typename T> class thread_local_variable final { private: wrapper<T> *pointer; public: template <typename ...Args> thread_local_variable(Args &&...args) { wrapper<T> v(args...); pointer = &v; } T &get() { return pointer->value; } }; non_copyable &fn() { thread_local_variable<non_copyable> v; return v.get(); } --- CUT ---- args here is {}. I suspect an empty arguments it not being treated correctly.
next prev parent reply other threads:[~2015-06-01 13:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-01 12:40 [Bug c++/66360] New: " programmerjake at gmail dot com 2015-06-01 13:30 ` pinskia at gcc dot gnu.org [this message] 2015-06-01 14:17 ` [Bug c++/66360] " redi at gcc dot gnu.org 2020-08-30 18:17 ` egallager at gcc dot gnu.org 2020-11-04 15:10 ` redi 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-66360-4-f3ABPjrTRX@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).