Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of msebor@gmail.com designates
 209.85.146.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:organization:user-agent:mime-version:to:subject:content-type:content-transfer-encoding:sender;
        b=cIZ8rO1xZb9s0Trort9yiBLoZi/RVlL1QIJTeHUrX7FR+ZDekmUCoHdMNnSrxvrs8bz67nqvy4hp9GxpV69Ig+9VR/wkKGwGkpCLqFcROLgP1biXkt8lHVLd6w/NA7uT3cDhNMtfJsJahZxMfUF7hJnBVDsw7sFac249BSb8RRY=
Message-ID: <46774B7B.8070105@roguewave.com>
Date: Mon, 18 Jun 2007 21:20:27 -0600
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.8.0.12) Gecko/20070531 Fedora/1.0.9-1.fc6 pango-text SeaMonkey/1.0.9
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: status of thread safety tests
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: Martin Sebor <msebor@gmail.com>

I've been working on a document listing the thread safety tests
in stdcxx/trunk and their current status:

   http://people.apache.org/~sebor/thread_safety_tests.html

The goal is to have a full understanding of all the problems
and address them (or at least the most important ones) in the
final 4.2.0 release.

The document is still a work in progress, as is the test suite.
Not all tests have been migrated from the Rogue Wave test suite
in Perforce over to ASF Subversion. For those tests the links
that point to the Perforce source repository won't work.