Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 Jan 2017 16:40:35 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-threads@FreeBSD.org
Subject:   [Bug 215709] Use of thread_local produces linking errors [now with gcc]
Message-ID:  <bug-215709-16-KuMupm2OYm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-215709-16@https.bugs.freebsd.org/bugzilla/>
References:  <bug-215709-16@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215709

--- Comment #2 from Hannes Hauswedell <h2+fbsdports@fsfe.org> ---
(In reply to Konstantin Belousov from comment #1)

ok, I have opened an issue over at gcc:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D78968

Let's see what they say.

Concerning your proposed workaround: Since all the magic is done by cmake I
have little influence on the order, although it does seem like it gets into
libstdc++ first (see the "first defined here").

I have a different workaround in the code that I have also been using for
FreeBSD<11 + LLVM and that I am now just expanding so that thread_local is =
just
never used on FreeBSD right now.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215709-16-KuMupm2OYm>