Here are a couple of articles from the Intel Knowledge Base that don't
appear to come with a restrictive license or even a copyright. The code
is Windows-specific but it should be possible to translate it to
something understandable to gcc and other compilers (Sun C++ on x86).
How to Determine
Martin Sebor wrote:
Here are a couple of articles from the Intel Knowledge Base that don't
appear to come with a restrictive license or even a copyright. The code
is Windows-specific but it should be possible to translate it to
something understandable to gcc and other compilers (Sun C++ on
William A. Rowe, Jr. wrote:
Martin Sebor wrote:
Here are a couple of articles from the Intel Knowledge Base that don't
appear to come with a restrictive license or even a copyright. The code
is Windows-specific but it should be possible to translate it to
something understandable to gcc and
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED] On Behalf Of Martin Sebor
Sent: Thursday, July 26, 2007 7:50 PM
To: stdcxx-dev@incubator.apache.org
Subject: Re: atomic tests timing out on Windows
As I understand the technology, the benefit of hyperthreading
Farid Zaripov wrote:
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED] On Behalf Of Martin Sebor
Sent: Thursday, July 26, 2007 6:17 AM
To: stdcxx-dev@incubator.apache.org
Subject: Re: atomic tests timing out on Windows
That tests works fine, but slow. This is because
Looks like the two atomic tests, atomic_add.exe and atomic_xchg.exe,
are timing out in some (optimized) MSVC builds on Windows.
First, the timeout seems to be set to 180 seconds on Windows but 300
seconds on all other platforms. I think we should increase it on
Windows to make it consistent.
Farid Zaripov wrote:
Looks like the two atomic tests, atomic_add.exe and atomic_xchg.exe,
are timing out in some (optimized) MSVC builds on Windows.
First, the timeout seems to be set to 180 seconds on Windows but 300
seconds on all other platforms. I think we should increase it on
Windows to
Looks like the two atomic tests, atomic_add.exe and atomic_xchg.exe,
are timing out in some (optimized) MSVC builds on Windows.
First, the timeout seems to be set to 180 seconds on Windows but 300
seconds on all other platforms. I think we should increase it on
Windows to make it consistent. How
