From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-382361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 24256 invoked by alias); 3 Feb 2012 02:16:15 -0000
Received: (qmail 24248 invoked by uid 22791); 3 Feb 2012 02:16:14 -0000
X-SWARE-Spam-Status: No, hits=-2.9 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
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; Fri, 03 Feb 2012 02:16:00 +0000
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51906] thread lock test failures on darwin11 under Xcode 4.2
Date: Fri, 03 Feb 2012 02:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: howarth at nitro dot med.uc.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.0
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51906-4-QGt9Pya6wQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51906-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-02/txt/msg00295.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51906

--- Comment #37 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-02-03 02:14:52 UTC ---
(In reply to comment #36)
> is there a Mac OS X version macro that libstdc++ can check to workaround the
> bug, or should we just assume it will be fixed and users will have a working
> version?

You would probably have to use Availability.h and something like...

        #ifdef __MAC_OS_X_VERSION_MIN_REQUIRED
            // code only compiled when targeting Mac OS X and not iPhone
            // note use of 1070 instead of __MAC_10_7
            #if __MAC_OS_X_VERSION_MIN_REQUIRED == 1070
                // code in here to run targeting Lion
            #else
                // code here can assume targeting pre- or post-Lion.
            #endif
        #endif