From patchwork Mon Feb 6 21:34:40 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jonathan Wakely X-Patchwork-Id: 139806 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) by ozlabs.org (Postfix) with SMTP id EE25F1007D1 for ; Tue, 7 Feb 2012 08:35:00 +1100 (EST) Comment: DKIM? See http://www.dkim.org DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=gcc.gnu.org; s=default; x=1329168901; h=Comment: DomainKey-Signature:Received:Received:Received:Received: MIME-Version:Received:Received:In-Reply-To:References:Date: Message-ID:Subject:From:To:Content-Type:Mailing-List:Precedence: List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender: Delivered-To; bh=pmse2omu3nSYd2S8WhdlvqdExUg=; b=dseg6VoQ1QepQTS 10KFVXDit8WqcB+jP6qqSCJmp9LxpHqft1DuPMERlQTiw0yyocSHAAxnGYN6LCom sWXM85y8quGY2eNOhKAYNW30Ls+1SKmhNiRfc0W0+nfumydjSSB1uADr8VmvXWGf DlPtJRArwL+yQUmkXsTma78+P/M4= Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gcc.gnu.org; h=Received:Received:X-SWARE-Spam-Status:X-Spam-Check-By:Received:Received:MIME-Version:Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Content-Type:Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender:Delivered-To; b=mXpQbI4OJCT8Ocq+7y7+LiTtATZmth/NZoAZZCRL99EiLcRAwvbuzvIw8nN0X2 u1A2DRVezSnQQFIQYOor144nmNBBITwDLqRw3DYcLJUJ3BFD7WNWBy1dkuqavc/u xa++t8bz3eoXDAsSHKxJD/6q2DmRFGFAT9AacVqaDb6n0=; Received: (qmail 13689 invoked by alias); 6 Feb 2012 21:34:56 -0000 Received: (qmail 13536 invoked by uid 22791); 6 Feb 2012 21:34:55 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL, BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-lpp01m010-f47.google.com (HELO mail-lpp01m010-f47.google.com) (209.85.215.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 06 Feb 2012 21:34:42 +0000 Received: by lahc1 with SMTP id c1so3680933lah.20 for ; Mon, 06 Feb 2012 13:34:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.123.10 with SMTP id lw10mr11728706lab.35.1328564080600; Mon, 06 Feb 2012 13:34:40 -0800 (PST) Received: by 10.112.39.42 with HTTP; Mon, 6 Feb 2012 13:34:40 -0800 (PST) In-Reply-To: References: Date: Mon, 6 Feb 2012 21:34:40 +0000 Message-ID: Subject: Re: libstdc++/52104 - fix linker error for non-TLS targets From: Jonathan Wakely To: "libstdc++" , gcc-patches Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org And fix a linker error (which I can't reproduce) on TLS targets, which can use an explicit instantiation because it doesn't refer to an unnamed closure type. PR libstdc++/52128 * src/c++11/future.cc: Add explicit instantiation. Tested x86_64-linux, powerpc-linux, i686-linux, x86_64-netbsd, committed to trunk. diff --git a/libstdc++-v3/src/c++11/future.cc b/libstdc++-v3/src/c++11/future.cc index 61a9729..a488139 100644 --- a/libstdc++-v3/src/c++11/future.cc +++ b/libstdc++-v3/src/c++11/future.cc @@ -90,6 +90,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION // Explicit instantiation due to -fno-implicit-instantiation. template void call_once(once_flag&, void (thread::*&&)(), reference_wrapper&&); + template _Bind_simple_helper>::__type __bind_simple(void (thread::*&&)(), reference_wrapper&&); #endif #endif