From owner-freebsd-threads@freebsd.org  Mon Jan  2 16:40:36 2017
Return-Path: <owner-freebsd-threads@freebsd.org>
Delivered-To: freebsd-threads@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A923C9CD06
 for <freebsd-threads@mailman.ysv.freebsd.org>;
 Mon,  2 Jan 2017 16:40:36 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1A2571305
 for <freebsd-threads@FreeBSD.org>; Mon,  2 Jan 2017 16:40:36 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v02GeZrb015869
 for <freebsd-threads@FreeBSD.org>; Mon, 2 Jan 2017 16:40:35 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 215709] Use of thread_local produces linking errors [now with
 gcc]
Date: Mon, 02 Jan 2017 16:40:35 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: threads
X-Bugzilla-Version: 11.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: h2+fbsdports@fsfe.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads/>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jan 2017 16:40:36 -0000

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.=