On 28/03/13 12:03, Steven Watanabe wrote:
AMDG
The list of required toolsets in explicit-failures-markup.xml is out-dated. Therefore, if no one objects, I propose setting it to the following:
msvc-10.0, msvc-11.0, gcc-4.6, gcc-4.7, clang-darwin-11, clang-darwin-4.2.1, clang-linux-3.1, clang-linux-3.2, gcc-mingw-4.7, gcc-mingw-4.6
I'm guessing that would look like: Linux: gcc-4.6, gcc-4.7, clang-linux-3.1, clang-linux-3.2, OSX: clang-darwin-11, clang-darwin-4.2.1 Windows: msvc-10.0, msvc-11.0, gcc-4.6, gcc-4.7 cc-mingw-4.7, gcc-mingw-4.6 Just as additional information, the current list: Linux: gcc-4.1.3_linux, gcc-4.2.1 gcc-4.2.1_linux_x86_64, intel-linux-9.0, OSX: darwin-4.0.1, Windows: intel-vc8-win-10.0 intel-win-10.0 msvc-7.1, msvc-8.0, msvc-8.0_64 HP: acc gcc-4.2.1_hpux_ia64 SunOS: gcc-4.1.2_sunos_i86pc, And "primary test compilers" for release 1.53: Linux: GCC: 4.1.2, 4.2.4, 4.4.4, 4.5.3, 4.6.3, 4.7.2 GCC, C++11 mode: 4.4.4, 4.5.3, 4.6.3, 4.7.2 Intel: 11.1, 12.1 LLVM Clang: 2.8 LLVM Clang, with libc++: 3.2 OS X: GCC: 4.4.7 GCC, C++11 mode: 4.4.4 Intel: 11.1, 12.0 Windows: Visual C++: 9.0, 10.0 FreeBSD: GCC: 4.2.1, 32 and 64 bit The Intel compilers stand out as currently untested, so I guess it makes sense to drop them since nobody cares enough to run tests. Also last visible test run on AIX was 2008, and I can't see any runs for HP or SunOS.
The sole effect of this is to determine which toolsets appear in the issues list: http://www.boost.org/development/tests/trunk/developer/issues.html
Certainly dropping msvc-8 and gcc-4.2.1 would make that list look different. Adding the newer platforms will make it a lot more relevant. I seem to recall FreeBSD moving over to clang at some point, so hopefully they too can move beyond GCC 4.2.1 I say go for it... change it on trunk, observe, merge to release. Ben