From: Dongsheng Song <dongsheng.song@gmail.com>
To: pthreads-win32@sources.redhat.com
Subject: Re: VCE test failed under Microsoft Visual Studio .NET 2003
Date: Tue, 08 Mar 2005 12:08:00 -0000 [thread overview]
Message-ID: <4b3406f0503080408532dcfc1@mail.gmail.com> (raw)
In-Reply-To: <4b3406f050304202047657da3@mail.gmail.com>
Visual C++ 2005 Express Edition Beta2 passed VC & VCE test(cvs 2005-03-08).
U:\xchg>cl
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50110.28 for 80x86
Copyright (C) Microsoft Corporation. All rights reserved.
usage: cl [ option... ] filename... [ /link linkoption... ]
On Sat, 5 Mar 2005 12:20:31 +0800, Dongsheng Song
<dongsheng.song@gmail.com> wrote:
> Yes, the Intel C++ 8.1 version passed VC & VCE test.
>
>
> On Fri, 04 Mar 2005 18:30:44 +1100, Ross Johnson
> <rpj@callisto.canberra.edu.au> wrote:
> > Hi,
> >
> > Thanks for the test suite patches re Intel C++ 8.1.
> >
> > VCE test failure is a known problem for VC6.0 and VC7.0. I will add
> > VS .NET 2003 to the list. See the BUGS file for more on this, but note
> > that the workaround described there doesn't work with recent snapshots,
> > although please try it if you have the time - it may provide clues.
> >
> > As far as anyone can tell, this isn't a problem in the library, but is
> > assumed to be a problem in the VC++ compiler series related to exception
> > frame unwinding, and possibly also related to optimisation levels. Try
> > tracing the exception and it simply seems to disappear.
> >
> > The GCE version tests pass, which supports the view that it's not a bug
> > in the library. Did the Intel C++ 8.1 version pass?
> >
> > It is generally recommended, for POSIX portability, that people use the
> > VC version rather than VCE version of the pthread dll - even for C++
> > applications. See the README file and FAQ file for discussion on this.
> >
> > Regards.
> > Ross
> >
> > On Thu, 2005-03-03 at 11:04 +0800, Dongsheng Song wrote:
> > > I using Microsoft Visual Studio .NET 2003 compile the latest
> > > pthread-win32 code, VC test passed, VCE test fail:
> > > ...
> > >
> > > cl /GX /TP /DPtW32NoCatchWarn /D__CLEANUP_CXX /O2 /Ob2 /W3 /WX /MD
> > > /nologo -I. s
> > > emaphore4.c /Fesemaphore4.exe /link /INCREMENTAL:NO pthreadVCE1.lib
> > > ws2_32.lib
> > > semaphore4.c
> > > ... Running VCE test: semaphore4.exe
> > > Assertion failed: (-value == (MAX_COUNT - 1)), file semaphore4.c, line 122
> > > NMAKE : fatal error U1077: ".\semaphore4.exe" : return code "0x1"
> > > Stop.
> > >
> > >
> >
> >
>
next prev parent reply other threads:[~2005-03-08 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 3:04 Dongsheng Song
2005-03-03 3:19 ` Intel C++ 8.1 fix for pthread-win32 test code Dongsheng Song
2005-03-04 7:30 ` VCE test failed under Microsoft Visual Studio .NET 2003 Ross Johnson
[not found] ` <4b3406f050304202047657da3@mail.gmail.com>
2005-03-08 12:08 ` Dongsheng Song [this message]
2005-03-08 13:33 ` Ross Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b3406f0503080408532dcfc1@mail.gmail.com \
--to=dongsheng.song@gmail.com \
--cc=pthreads-win32@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).