From owner-freebsd-toolchain@FreeBSD.ORG  Thu Feb 19 08:57:04 2015
Return-Path: <owner-freebsd-toolchain@FreeBSD.ORG>
Delivered-To: freebsd-toolchain@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 54BC7F91
 for <freebsd-toolchain@FreeBSD.org>; Thu, 19 Feb 2015 08:57:04 +0000 (UTC)
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 3AE63355
 for <freebsd-toolchain@FreeBSD.org>; Thu, 19 Feb 2015 08:57:04 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1J8v3kA034526
 for <freebsd-toolchain@FreeBSD.org>; Thu, 19 Feb 2015 08:57:03 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-toolchain@FreeBSD.org
Subject: [Bug 192320] Use of thread_local produces linking errors on system
 version of clang++
Date: Thu, 19 Feb 2015 08:57:04 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: misc
X-Bugzilla-Version: 10.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: tijl@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-toolchain@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-192320-29464-rVQHIWXFF0@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-192320-29464@https.bugs.freebsd.org/bugzilla/>
References: <bug-192320-29464@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2015 08:57:04 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192320

--- Comment #5 from Tijl Coosemans <tijl@FreeBSD.org> ---
(In reply to David Chisnall from comment #4)
That's what glibc seems to do.  When a thread calls dlclose its thread_local
variables are destroyed, but if there are other threads with thread_local
variables the DSO is kept in memory until those variables are destroyed (when
the threads exit or call dlclose).

https://sourceware.org/glibc/wiki/Destructor%20support%20for%20thread_local%20variables

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