|
From: | hjl.tools at gmail dot com |
Subject: | [Bug ld/22727] [2.30, 2.31 regression] Thousands of EH-related execution failures on SPARC |
Date: | Thu, 18 Jan 2018 13:17:56 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=22727 --- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Eric Botcazou from comment #8) > > This implies that ld testsuite coverage in binutils for Sparc is very > > poor. Can you extract some ld tesctcases from GCC tests? > > Are gcc.dg/torture/tls/run-gd.c or gcc.dg/torture/tls/run-ld.c good enough? > > === gcc tests === > > Schedule of variations: > unix > > Running target unix > Using /usr/share/dejagnu/baseboards/unix.exp as board description file for > target. > Using /usr/share/dejagnu/config/unix.exp as generic interface file for > target. > Using /home/ebotcazou/src-7.3/gcc/testsuite/config/default.exp as > tool-and-target-specific interface file. > Running /home/ebotcazou/src-7.3/gcc/testsuite/gcc.dg/tls/tls.exp ... > Running /home/ebotcazou/src-7.3/gcc/testsuite/gcc.dg/torture/tls/tls.exp ... > FAIL: gcc.dg/torture/tls/run-gd.c -O0 -pie -fpie execution test > FAIL: gcc.dg/torture/tls/run-gd.c -O1 -pie -fpie execution test > FAIL: gcc.dg/torture/tls/run-gd.c -O2 -pie -fpie execution test > FAIL: gcc.dg/torture/tls/run-gd.c -O3 -g -pie -fpie execution test > FAIL: gcc.dg/torture/tls/run-gd.c -Os -pie -fpie execution test > FAIL: gcc.dg/torture/tls/run-gd.c -O0 -pie -fPIE execution test > FAIL: gcc.dg/torture/tls/run-gd.c -O1 -pie -fPIE execution test > FAIL: gcc.dg/torture/tls/run-gd.c -O2 -pie -fPIE execution test > FAIL: gcc.dg/torture/tls/run-gd.c -O3 -g -pie -fPIE execution test > FAIL: gcc.dg/torture/tls/run-gd.c -Os -pie -fPIE execution test > FAIL: gcc.dg/torture/tls/run-ld.c -O0 -pie -fpie execution test > FAIL: gcc.dg/torture/tls/run-ld.c -O1 -pie -fpie 2 blank line(s) in > output > FAIL: gcc.dg/torture/tls/run-ld.c -O1 -pie -fpie (test for excess errors) > FAIL: gcc.dg/torture/tls/run-ld.c -O1 -pie -fpie execution test > FAIL: gcc.dg/torture/tls/run-ld.c -O2 -pie -fpie 2 blank line(s) in > output > FAIL: gcc.dg/torture/tls/run-ld.c -O2 -pie -fpie (test for excess errors) > FAIL: gcc.dg/torture/tls/run-ld.c -O2 -pie -fpie execution test > FAIL: gcc.dg/torture/tls/run-ld.c -O3 -g -pie -fpie 2 blank line(s) in > output > FAIL: gcc.dg/torture/tls/run-ld.c -O3 -g -pie -fpie (test for excess > errors) > FAIL: gcc.dg/torture/tls/run-ld.c -O3 -g -pie -fpie execution test > FAIL: gcc.dg/torture/tls/run-ld.c -Os -pie -fpie 2 blank line(s) in > output > FAIL: gcc.dg/torture/tls/run-ld.c -Os -pie -fpie (test for excess errors) > FAIL: gcc.dg/torture/tls/run-ld.c -Os -pie -fpie execution test > FAIL: gcc.dg/torture/tls/run-ld.c -O0 -pie -fPIE execution test > FAIL: gcc.dg/torture/tls/run-ld.c -O1 -pie -fPIE 2 blank line(s) in > output > FAIL: gcc.dg/torture/tls/run-ld.c -O1 -pie -fPIE (test for excess errors) > FAIL: gcc.dg/torture/tls/run-ld.c -O1 -pie -fPIE execution test > FAIL: gcc.dg/torture/tls/run-ld.c -O2 -pie -fPIE 2 blank line(s) in > output > FAIL: gcc.dg/torture/tls/run-ld.c -O2 -pie -fPIE (test for excess errors) > FAIL: gcc.dg/torture/tls/run-ld.c -O2 -pie -fPIE execution test > FAIL: gcc.dg/torture/tls/run-ld.c -O3 -g -pie -fPIE 2 blank line(s) in > output > FAIL: gcc.dg/torture/tls/run-ld.c -O3 -g -pie -fPIE (test for excess > errors) > FAIL: gcc.dg/torture/tls/run-ld.c -O3 -g -pie -fPIE execution test > FAIL: gcc.dg/torture/tls/run-ld.c -Os -pie -fPIE 2 blank line(s) in > output > FAIL: gcc.dg/torture/tls/run-ld.c -Os -pie -fPIE (test for excess errors) > FAIL: gcc.dg/torture/tls/run-ld.c -Os -pie -fPIE execution test It looks like that PIE is broken on Sparc. This could be a dup of PR 22263. -- You are receiving this mail because: You are on the CC list for the bug.
[Prev in Thread] | Current Thread | [Next in Thread] |