From 40b0350ef8feea44cdfcec80cacff426e57f4631 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 1 Dec 2016 13:53:53 +0100 Subject: gcc: Re-run after system updates --- open_issues/gcc.mdwn | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) (limited to 'open_issues/gcc.mdwn') diff --git a/open_issues/gcc.mdwn b/open_issues/gcc.mdwn index f5164e33..fd4c49ee 100644 --- a/open_issues/gcc.mdwn +++ b/open_issues/gcc.mdwn @@ -1062,7 +1062,8 @@ a050099a416f013bda35832b878d9a57b0cbb231 (gcc-6-branch branch point; Here's a log of a GCC build run; this is from Git commit a050099a416f013bda35832b878d9a57b0cbb231 (gcc-6-branch branch point; -2016-04-15), run on kepler.SCHWINGE +2016-04-15), plus *libstdc++ RLIMIT changes* ([[!message-id +"8760n66mky.fsf@euler.schwinge.homeip.net"]]), run on kepler.SCHWINGE and laplace.SCHWINGE. $ export LC_ALL=C @@ -1083,8 +1084,8 @@ until these is auto-detected/fixed/ported for GNU Hurd. `/include` for GNU Hurd. Explicit `--enable-multiarch` because *auto check [is disabled if] configured with --native-system-header-dir*. -This takes up around 4.8 GiB, and runs for [[4 h 18 min|performance#measure]] -on kepler.SCHWINGE and [[5 h 6 min|performance#measure]] on laplace.SCHWINGE. +This takes up around 4.8 GiB, and runs for [[3 h 57 min|performance#measure]] +on kepler.SCHWINGE and [[3 h 45 min|performance#measure]] on laplace.SCHWINGE. @@ -830,8 +830,8 @@ formats, and more emulation vectors. $ make install 2>&1 | tee log_install [...] -This takes up around 220 MiB, and runs for [[0 min|performance#measure]] on -kepler.SCHWINGE and [[2 min|performance#measure]] on laplace.SCHWINGE. +This takes up around 250 MiB, and runs for [[0 min|performance#measure]] on +kepler.SCHWINGE and [[3 min|performance#measure]] on laplace.SCHWINGE. ## Analysis @@ -843,10 +843,21 @@ kepler.SCHWINGE and [[2 min|performance#measure]] on laplace.SCHWINGE. # Testsuite - $ make -k check 2>&1 | tee log_test +At least for GNU/Linux, Debian's GCC 6 is configured with +`--enable-default-pie` -- which the *gdb*, *gold*, and *ld* testsuites don't +like, so we have to cancel that for testing. +`CC_FOR_TARGET` and `CXX_FOR_TARGET` in `RUNTESTFLAGS` is considered by the *gdb* testsuite, +`CC_FOR_TARGET` and `CXX_FOR_TARGET` on the `make` command line by the *ld* testsuite, +`CC` and `CXX` on the `make` command line by the *gold* testsuite +but only when invoked (from the top level) as `make check-gold` and not when run as part of `make check`... +I couldn't figure out a command-line variant for *gold* testsuite, +so instead we apply an ugly hack to `gold/testsuite/Makefile`. + + $ sed -e 's%^\([A-Z]\+ = g..-6\)%override \1 -fno-pie -fno-PIE -no-pie%g' -i gold/testsuite/Makefile + $ make -k check RUNTESTFLAGS=CC_FOR_TARGET='gcc-6\ -fno-pie\ -fno-PIE\ -no-pie'\ CXX_FOR_TARGET='g++-6\ -fno-pie\ -fno-PIE\ -no-pie' CC_FOR_TARGET='gcc-6 -fno-pie -fno-PIE -no-pie' CXX_FOR_TARGET='g++-6 -fno-pie -fno-PIE -no-pie' 2>&1 | tee log_test [...] -This runs for [[23 min|performance#measure]] on kepler.SCHWINGE and [[73 +This runs for [[24 min|performance#measure]] on kepler.SCHWINGE and [[86 min|performance#measure]] on laplace.SCHWINGE. When running `make -k check 2>&1 | tee log_test`, at the end of the testsuite diff --git a/open_issues/gcc.mdwn b/open_issues/gcc.mdwn index c742f06e..7850d024 100644 --- a/open_issues/gcc.mdwn +++ b/open_issues/gcc.mdwn @@ -1061,6 +1061,12 @@ a050099a416f013bda35832b878d9a57b0cbb231 (gcc-6-branch branch point; ee1bfdb0d611ed2e1057071f39589e6ebcd87983 `Remove __seg_tls before first release`. + * `--enable-default-pie` + + On 2016-12-05 noticed that per `gcc -v` output, `gcc version 6.2.1 20161124 + (Debian 6.2.1-5)` for GNU/Linux is configured with + `--enable-default-pie`, but GNU/Hurd is not. + # Build diff --git a/toolchain/logs b/toolchain/logs index 9f697cf0..f7e923e5 160000 --- a/toolchain/logs +++ b/toolchain/logs @@ -1 +1 @@ -Subproject commit 9f697cf053de6605ac1f5e5e9a3b22b889ba3f6d +Subproject commit f7e923e5eda4eb2148cdac492f0f77dc2f771528 -- cgit v1.2.3