From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11167 invoked by alias); 27 Sep 2010 18:34:52 -0000 Received: (qmail 11082 invoked by uid 22791); 27 Sep 2010 18:34:51 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,MISSING_MID X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 27 Sep 2010 18:34:47 +0000 From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/45693] [4.6 regression] All Tru64 UNIX EH tests fail X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Mon, 27 Sep 2010 22:13:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-09/txt/msg02944.txt.bz2 Message-ID: <20100927221300.r20nhIfBNV1vjyINXDTc-5rJKuW79FOZge8ESVl_WSY@z> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45693 --- Comment #5 from Iain Sandoe 2010-09-27 18:34:46 UTC --- (In reply to comment #4) > (In reply to comment #3) > > But that support was present before, and still GCC_CHECK_TLS didn't > > detect it before Iain's patch. Something is certainly fishy here... > > His patch was explicitly to fix checking for TLS when emulated TLS was used. > Sometimes it would detect it as working and other times it would not. As I recall, the patch was to circumvent a race condition - which manifest most frequently in the decision as to whether libgomp used TLS or not. It's odd that after this time a problem should show in libstdc++ (which was never, AFAIR flagged up in the original problem series). As for a platform with TLS - Darwin is regularly testing libstdc++ on powepc, and x86 .. so there must be some corner case at work.