Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (nike.apache.org: domain of stefan.teleman@gmail.com
 designates 209.85.220.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <9ippq5k7j87.fsf@e103010-lin.cambridge.arm.com>
References: <40394653-8FCC-4D04-A108-2C650AF8F95B@hates.ms>
	<504FE7F9.90102@gmail.com>
	<504FF10E.8020506@hates.ms>
	<CALdE9OB9XPF6f+nH9S-=9NAE0Fj2D44JmXudD00-BXrk0=bU3w@mail.gmail.com>
	<50508849.4070708@hates.ms>
	<CALdE9OA-nNDcgzb7evuYuX2m_1CS7VW9krdaLO64v5OfHBRGcQ@mail.gmail.com>
	<CALdE9OC4y-MsNpjBtYMxoxuc-U3JLGcVAwaeDUWXa_18zauMAQ@mail.gmail.com>
	<50547C22.1000604@hates.ms>
	<CALdE9OBXbd5SKWSUtc_5_GznSDmruZuwLxJ2Xeoc1YZ3F_UdPA@mail.gmail.com>
	<5054EAB7.5050609@hates.ms>
	<CALdE9OChNHO9FCDntmGfoEOC0bVgE=QpcGJ+GSTJGJxUK4981Q@mail.gmail.com>
	<5055EE63.6090004@hates.ms>
	<CALdE9OD3vLnh-VoeBva9rdA-my19LTMPhofrUdQcr-CnecGzkw@mail.gmail.com>
	<50566461.4080101@hates.ms>
	<CALdE9ODn2=smyJbwO5mwVPNTP=GrPSaTkP6mqaAL931J2JNO-g@mail.gmail.com>
	<50571B8B.6020202@hates.ms>
	<CALdE9OCF1+gcZcaVB0JtjRHJhcVBP+nA5wn-ia8WzbCQSCcJ_w@mail.gmail.com>
	<50573F0F.3090908@hates.ms>
	<CALdE9OAwYw9ffHrLGzn_wkYrMNbcaiP2q1cu4BGt0GnJmJ+0pg@mail.gmail.com>
	<5057413C.3060207@hates.ms>
	<9ippq5k7j87.fsf@e103010-lin.cambridge.arm.com>
Date: Mon, 17 Sep 2012 11:44:37 -0400
Message-ID: 
 <CALdE9OCwfjhR9h6Y396=E9T=ndR15Xd-b=Ge7zbtzgyjWqQ6zg@mail.gmail.com>
Subject: Re: STDCXX-1056 [was: Re: STDCXX forks]
From: Stefan Teleman <stefan.teleman@gmail.com>
To: dev@stdcxx.apache.org
Content-Type: text/plain; charset=UTF-8

On Mon, Sep 17, 2012 at 11:38 AM, Wojciech Meyer <wojciech.meyer@arm.com> wrote:

> so which compilers do fail? You know, some of them might use the same
> component.

Intel Compiler/Thread Analyzer on Linux, SunPro Compiler/Thread
Analyzer on Linux and Solaris (Intel and SPARC). All three of them
show the same exact problems.

The Intel Compilers and the SunPro Compilers have nothing in common
with each other.

-- 
Stefan Teleman
KDE e.V.
stefan.teleman@gmail.com