gcc/libgomp/testsuite/libgomp.oacc-c++
Thomas Schwinge fdc9db2539 [testsuite] Unset 'offload_target' after use
..., so that we don't leak this into '*.exp' files running later.

This is relevant after commit efc16503ca "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.
2020-07-24 14:00:43 +02:00
..
c++.exp
declare-1.C
declare-pr94120.C
deep-copy-12.C
deep-copy-13.C
firstprivate-mappings-1.C
non-scalar-data.C
pr71959-aux.cc
pr71959.C
ref-1.C
routine-1-auto.C
routine-1-template-auto.C
routine-1-template-trailing-return-type.C
routine-1-template.C
routine-1-trailing-return-type.C
template-reduction.C
this.C