RE: status of thread safety tests

[Eric Lemings <le...@roguewave.com>]

Could you add a brief note on how the tests were built and executed?
Specifically, were they built and executed with gcc using binary
instrumentation or with icc using dynamic instrumentation?

Thanks.
 

> -----Original Message-----
> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of Martin Sebor
> Sent: Monday, June 18, 2007 9:20 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: status of thread safety tests
> 
> 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.
> 

Re: status of thread safety tests

[Martin Sebor <se...@roguewave.com>]

Eric Lemings wrote:
> Could you add a brief note on how the tests were built and executed?
> Specifically, were they built and executed with gcc using binary
> instrumentation or with icc using dynamic instrumentation?

Good suggestion! I used icc with the -tcheck option to compile
and link the tests and ran the executables through the tcheck_cl
driver (silly name, btw.) I would expect the results to be the
same when I use gcc. I've tried using it but didn't actually
compare the results. It might be an interesting project. Let
me put the info on the page the next time I update it.

Martin

> 
> Thanks.
>  
> 
>> -----Original Message-----
>> From: Martin Sebor [mailto:msebor@gmail.com] On Behalf Of Martin Sebor
>> Sent: Monday, June 18, 2007 9:20 PM
>> To: stdcxx-dev@incubator.apache.org
>> Subject: status of thread safety tests
>>
>> 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.
>>