diff options
| author | Alexandre Oliva <oliva@adacore.com> | 2020-04-08 12:41:52 -0300 |
|---|---|---|
| committer | Alexandre Oliva <oliva@gnu.org> | 2020-04-08 12:41:52 -0300 |
| commit | e4b84abcc46fb4270172584ac5a4b46d70e93259 (patch) | |
| tree | 05bfedfd6fbcedd8bd62b1137aad688efcb3c659 /libstdc++-v3/include/std/complex | |
| parent | 70df40cab6f268ba7f05c6d1421928cca0834ee3 (diff) | |
| download | gcc-e4b84abcc46fb4270172584ac5a4b46d70e93259.zip gcc-e4b84abcc46fb4270172584ac5a4b46d70e93259.tar.gz gcc-e4b84abcc46fb4270172584ac5a4b46d70e93259.tar.bz2 | |
require tls_runtime for tls execution test
All TLS execution tests require tls_runtime, not just tls; pr78796.c
is the only exception that is not otherwise limited to platforms known
to support it. I suppose that's an oversight. On a platform whose
linker is configured to disregard TLS relocations, this test compiles
and assembles successfully, but execution fails. The tls_runtime
requirement target avoids the noise from the expected failure.
for gcc/testsuite/ChangeLog
* gcc.dg/tls/pr78796.c: Require tls_runtime.
Diffstat (limited to 'libstdc++-v3/include/std/complex')
0 files changed, 0 insertions, 0 deletions