Re: VC++ 2005 beta1 fails with pthreads benchmark tests



um wrote:
> When the POSIX pthreads library for w32 release 2-2-0
> (http://sources.redhat.com/pthreads-win32/) is compiled with VC++6
> then it compiles and passes all the benchmark tests in the
> subdirectory "tests". Also, VC++ 2005 beta 1 compiles the tests fine,
> but here the following
> tests fail in execution:
>
> # semaphore1.pass \
> # condvar2.pass \
> # condvar2_1.pass \
> # mutex8.pass \
> # mutex8n.pass \
> # mutex8e.pass \
> # mutex8r.pass \
> # condvar3.pass \
> # condvar3_1.pass \
> # condvar3_2.pass \
> # condvar3_3.pass \
> # condvar4.pass \
> # condvar5.pass \
> # condvar6.pass \
> # condvar7.pass \
> # condvar8.pass \
> # condvar9.pass \
> # rwlock7.pass \
> # rwlock8.pass \
> # rwlock2_t.pass \
> # rwlock3_t.pass \
> # rwlock4_t.pass \
> # rwlock5_t.pass \
> # rwlock6_t.pass \
> # rwlock6_t2.pass \
> # spin4.pass \
>
> Why are there such differences in execution of the generated code
> between VC++6 and VC++2005 ? Is this due to bugs in the beta1,
> or is this the result of general differences between the two products?
> Are there any compiler/linker switches for backwards "compatibility"
> to VC++6?

You're going to need to post a lot more details to get a satisfying answer,
unless a pthreads-win32 expert happens to read this newsgroup.

I'd suggest examining a single failure in depth with the goal of producing a
simple small program that behaves differently on VC6 versus VC8 beta 1 (also
note that beta 2 was released lasts Friday).

-cd


.



Relevant Pages

  • Re: VC++ 2005 beta1 fails with pthreads benchmark tests
    ... >> then it compiles and passes all the benchmark tests in the ... >> tests fail in execution: ... >> Why are there such differences in execution of the generated code ... >> or is this the result of general differences between the two products? ...
    (microsoft.public.dotnet.languages.vc)
  • Re: VC++ 2005 beta1 fails with pthreads benchmark tests
    ... > then it compiles and passes all the benchmark tests in the ... > tests fail in execution: ... > Why are there such differences in execution of the generated code ... > or is this the result of general differences between the two products? ...
    (microsoft.public.dotnet.languages.vc)

Loading