diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2020-07-01 12:33:59 +0200 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2020-07-24 14:00:43 +0200 |
| commit | fdc9db25395e5a6e77069c04fe713f165a9c52a4 (patch) | |
| tree | 207631fdeb1534cb6ad2e91753b92c90312353e6 /gcc | |
| parent | 3407bfc136bb6b9cf8e25eb753b448b527590b3b (diff) | |
| download | gcc-fdc9db25395e5a6e77069c04fe713f165a9c52a4.zip gcc-fdc9db25395e5a6e77069c04fe713f165a9c52a4.tar.gz gcc-fdc9db25395e5a6e77069c04fe713f165a9c52a4.tar.bz2 | |
[testsuite] Unset 'offload_target' after use
..., so that we don't leak this into '*.exp' files running later.
This is relevant after commit efc16503ca10bc0e934e0bace5777500e4dc757a "handle
dumpbase in offloading, adjust testsuite" -- I was confused why in a
(simplified) testing sequence as follows:
default 'libgomp.c/c.exp'
default 'libgomp.oacc-c/c.exp'
'-m32' 'libgomp.c/c.exp'
'-m32' 'libgomp.oacc-c/c.exp'
..., the "'-m32' 'libgomp.c/c.exp'" variant would not execute any offloading
dump scanning. The reason is that the "default 'libgomp.oacc-c/c.exp'" variant
ends with 'offload_target=disable' set, so that's what the "'-m32'
'libgomp.c/c.exp'" variant would then see, in particular
'gcc/testsuite/lib/scanoffload.exp:scoff'.
libgomp/
* testsuite/libgomp.oacc-c++/c++.exp: Unset 'offload_target' after
use.
* testsuite/libgomp.oacc-c/c.exp: Likewise.
* testsuite/libgomp.oacc-fortran/fortran.exp: Likewise.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions