This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: running 4.4 libstdc++ testsuite using 4.5's libstdc++ shared library

From: Paolo Carlini <pcarlini at gmail dot com>
To: Matthias Klose <doko at ubuntu dot com>
Cc: Paolo Carlini <pcarlini at gmail dot com>, "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>
Date: Sat, 26 Jun 2010 13:57:14 +0200
Subject: Re: running 4.4 libstdc++ testsuite using 4.5's libstdc++ shared library
References: <4C25DB6E.1050705@ubuntu.com> <EF8FEFC6-42C5-4A0E-BEA1-EDE6ED4A48D1@oracle.com> <4C25E657.1020902@ubuntu.com>

Hi,

> How would I differentiate between a genuine problem and a problem in the testsuite?

Better: between a genuine runtime binary compatibility issue and nothing, because an old testsuite will never be completely suited for a more recent system. Anyway, no idea: my impression is that the noise (ie, false positives) with this type of testing is overwhelming, like seeing a low mass Higgs at Fermilab ;)

Paolo.

Ps: the condition_variable PR likely is also a bit pointless, we are not guaranteeing full runtime binary compatibility for all the c++0x exp features, sorry.

Follow-Ups:
- Re: running 4.4 libstdc++ testsuite using 4.5's libstdc++ shared library
  - From: Jonathan Wakely

References:
- running 4.4 libstdc++ testsuite using 4.5's libstdc++ shared library
  - From: Matthias Klose
- Re: running 4.4 libstdc++ testsuite using 4.5's libstdc++ shared library
  - From: Paolo Carlini
- Re: running 4.4 libstdc++ testsuite using 4.5's libstdc++ shared library
  - From: Matthias Klose

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]