Difference between revisions of "User:Allan/Toolchain"

From ArchWiki
Jump to: navigation, search
(binutils)
(binutils)
 
(22 intermediate revisions by the same user not shown)
Line 3: Line 3:
  
 
=Current Toolchain=
 
=Current Toolchain=
 +
 
==binutils==
 
==binutils==
* Version: 2.22-6 (20120323)
 
 
Test suite failures - i686 and x86_64:
 
 
FAIL: relro_test.sh
 
FAIL: exception_separate_shared_12_test
 
FAIL: exception_separate_shared_21_test
 
FAIL: initpri3b
 
 
* relro_test.sh
 
** requires 'dc' installed
 
* exception_separate_shared_{12,21}_test
 
** failure due to missing symbols with -Wl,--as-needed: http://sourceware.org/bugzilla/show_bug.cgi?id=12353 
 
* initpri3b
 
** ???
 
  
 +
* Version: 2.23.2-2
  
 
Test suite failures - i686 only:
 
Test suite failures - i686 only:
 
 
  FAIL: debug_msg.sh
 
  FAIL: debug_msg.sh
  
 
* debug_msg.sh
 
* debug_msg.sh
** ???
+
** http://sourceware.org/bugzilla/show_bug.cgi?id=15411
  
  
 
Test suite failures - x86_64 only:
 
Test suite failures - x86_64 only:
 +
FAIL: exception_static_test
  
FAIL: incremental_test_2
+
* exception_static_test
FAIL: incremental_test_3
+
** http://sourceware.org/bugzilla/show_bug.cgi?id=15407
FAIL: incremental_test_4
+
FAIL: incremental_test_5
+
FAIL: incremental_test_6
+
FAIL: incremental_copy_test
+
FAIL: incremental_common_test_1
+
FAIL: incremental_comdat_test_1
+
 
+
* all
+
** due to -Wl,-z,relro
+
* incremental_copy_test
+
** additionally -Wl,--as-needed
+
  
 
==glibc==
 
==glibc==
* Version: 2.14-4 (20110617)
 
  
Test suite failures (i686 and x86_64):
+
* Version: 2.17-5
make[2]: *** [/build/src/glibc-build/stdlib/tst-putenv.out] Error 1
+
make[2]: *** [/build/src/glibc-build/nptl/tst-cancel24] Error 1
+
make[2]: *** [/build/src/glibc-build/nptl/tst-tls6.out] Error 1
+
make[2]: *** [/build/src/glibc-build/rt/tst-cpuclock2.out] Error 1
+
make[2]: *** [/build/src/glibc-build/elf/noload.out] Error 1
+
make[2]: *** [/build/src/glibc-build/elf/nodelete2.out] Error 1
+
make[2]: *** [/build/src/glibc-build/elf/next.out] Error 1
+
make[2]: *** [/build/src/glibc-build/elf/reldep5.out] Error 127
+
make[2]: *** [/build/src/glibc-build/elf/reldep6.out] Error 1
+
make[2]: *** [/build/src/glibc-build/elf/reldep8.out] Error 134
+
make[2]: *** [/build/src/glibc-build/elf/unload4.out] Error 127
+
make[2]: *** [/build/src/glibc-build/elf/order2.out] Error 1
+
make[2]: *** [/build/src/glibc-build/elf/tst-initorder.out] Error 1
+
  
* rt/tst-cpuclock2.out is a "timing" issue and can be ignored
 
* the rest are be due to building the test-suite with -Wl,--as-needed.
 
  
 +
No test suite failures!
  
Test suite failures (x86_64 only):
 
make[2]: *** [/build/src/glibc-build/misc/tst-writev.out] Error 1
 
  
 
==gcc==
 
==gcc==
* Version: 4.6.1-1
 
  
Test suite failures (i686 and x86_64):
+
* Version: 4.8.0-3 (20130425)
FAIL: libgomp.graphite/force-parallel-1.c execution test
+
+
FAIL: libmudflap.c/pass49-frag.c execution test
+
FAIL: libmudflap.c/pass49-frag.c output pattern test
+
FAIL: libmudflap.c/pass49-frag.c execution test
+
FAIL: libmudflap.c/pass49-frag.c output pattern test
+
FAIL: libmudflap.c/pass49-frag.c (-static) execution test
+
FAIL: libmudflap.c/pass49-frag.c (-static) output pattern test
+
FAIL: libmudflap.c/pass49-frag.c (-static) execution test
+
FAIL: libmudflap.c/pass49-frag.c (-static) output pattern test
+
FAIL: libmudflap.c/pass49-frag.c (-O2) execution test
+
FAIL: libmudflap.c/pass49-frag.c (-O2) output pattern test
+
FAIL: libmudflap.c/pass49-frag.c (-O2) execution test
+
FAIL: libmudflap.c/pass49-frag.c (-O2) output pattern test
+
FAIL: libmudflap.c/pass49-frag.c (-O3) execution test
+
FAIL: libmudflap.c/pass49-frag.c (-O3) output pattern test
+
FAIL: libmudflap.c/pass49-frag.c (-O3) execution test
+
FAIL: libmudflap.c/pass49-frag.c (-O3) output pattern test
+
+
FAIL: 20_util/enable_shared_from_this/cons/constexpr.cc (test for excess errors)
+
FAIL: 20_util/shared_ptr/cons/constexpr.cc (test for excess errors)
+
FAIL: 20_util/unique_ptr/cons/constexpr.cc (test for excess errors)
+
FAIL: 20_util/weak_ptr/cons/constexpr.cc (test for excess errors)
+
FAIL: 30_threads/future/cons/constexpr.cc (test for excess errors)
+
FAIL: 30_threads/shared_future/cons/constexpr.cc (test for excess errors)
+
  
* libgomp.graphite:
+
Test suite failures - i686 and x86_64:
** Seen regularly on i686/x86_64 (in H. J. Lu's test runs) but no bug report...
+
* libmudflap failures:
+
** http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20003
+
* 20_util/* and 30_threads/*
+
** Due to use of -pipe in C{XX}FLAGS: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
+
  
 +
FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test
 +
FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test
 +
FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test
  
Test suite failures (i686 only):
+
* Has libmudflap ever passed...
FAIL: gfortran.dg/graphite/vect-pr40979.f90  -O  scan-tree-dump-times vect "vectorized 1 loops" 1
+
+
FAIL: libmudflap.c/fail40-frag.c output pattern test
+
FAIL: libmudflap.c/pass51-frag.c execution test
+
FAIL: libmudflap.c/pass51-frag.c execution test
+
FAIL: libmudflap.c/fail40-frag.c (-static) output pattern test
+
FAIL: libmudflap.c/pass51-frag.c (-static) execution test
+
FAIL: libmudflap.c/pass51-frag.c (-static) execution test
+
FAIL: libmudflap.c/fail40-frag.c (-O2) output pattern test
+
FAIL: libmudflap.c/pass51-frag.c (-O2) execution test
+
FAIL: libmudflap.c/pass51-frag.c (-O2) execution test
+
FAIL: libmudflap.c/fail40-frag.c (-O3) output pattern test
+
FAIL: libmudflap.c/pass51-frag.c (-O3) execution test
+
FAIL: libmudflap.c/pass51-frag.c (-O3) execution test
+
FAIL: libmudflap.cth/pass39-frag.c (-O2) (rerun *) execution test
+
FAIL: libmudflap.cth/pass39-frag.c (-O2) (rerun *) output pattern test
+
  
* gfortran.dg/graphite/vect-pr40979.f90
 
** http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48497
 
  
 +
==linux-api-headers==
  
Test suite failures (x86_64 only):
+
* Version: 3.8.4-1
FAIL: ./tmp.go execution,  -O2 -g
+
  
==linux-api-headers==
 
* Version: 2.6.39.1-1
 
  
 
==Dependencies==
 
==Dependencies==
  
 
The following packages were used in generating the test suite results for the current toolchain:
 
The following packages were used in generating the test suite results for the current toolchain:
  cloog-0.16.2-1
+
  cloog-0.18.0-1
  isl-0.06-1
+
  isl-0.11.2-1
  gmp-5.0.2-1
+
  gmp-5.1.1-1
  libmpc-0.9-1
+
  libmpc-1.0.1-1
  mpfr-3.0.1-1
+
  mpfr-3.1.2-1
ppl-0.11.2-1
+
  zlib-1.2.7-1
  zlib-1.2.5-3
+
  
 
Any updates to these packages must pass their respective test suite completely before entering [testing].  In general it is not necessary to rerun the toolchain packages test suite on updates of these packages unless an soname bump has occurred.
 
Any updates to these packages must pass their respective test suite completely before entering [testing].  In general it is not necessary to rerun the toolchain packages test suite on updates of these packages unless an soname bump has occurred.

Latest revision as of 22:17, 29 April 2013

Overview

These are notes on the current state of the Arch Linux toolchain (gcc, glibc, binutils, linux-api-headers and their dependencies). This will record all known testsuite failures so that they can be investigated. Future toolchain rebuilds should not suffer from any additional (unexpected) testsuite failures and ideally should fix the current issues...

Current Toolchain

binutils

  • Version: 2.23.2-2

Test suite failures - i686 only:

FAIL: debug_msg.sh


Test suite failures - x86_64 only:

FAIL: exception_static_test

glibc

  • Version: 2.17-5


No test suite failures!


gcc

  • Version: 4.8.0-3 (20130425)

Test suite failures - i686 and x86_64:

FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test
  • Has libmudflap ever passed...


linux-api-headers

  • Version: 3.8.4-1


Dependencies

The following packages were used in generating the test suite results for the current toolchain:

cloog-0.18.0-1
isl-0.11.2-1
gmp-5.1.1-1
libmpc-1.0.1-1
mpfr-3.1.2-1
zlib-1.2.7-1

Any updates to these packages must pass their respective test suite completely before entering [testing]. In general it is not necessary to rerun the toolchain packages test suite on updates of these packages unless an soname bump has occurred.