aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2022-02-21 20:02:13 +0100
committerTom de Vries <tdevries@suse.de>2022-02-22 10:23:20 +0100
commit6263b656c8fcfc6d7e1d2af55a88bc0429a4b352 (patch)
treef80185f64e7855eff6e3f575b71675148d8094d1 /gcc
parentf0ae4257e3f939d186e9092e2b5724a9e3ce8ea6 (diff)
downloadgcc-6263b656c8fcfc6d7e1d2af55a88bc0429a4b352.zip
gcc-6263b656c8fcfc6d7e1d2af55a88bc0429a4b352.tar.gz
gcc-6263b656c8fcfc6d7e1d2af55a88bc0429a4b352.tar.bz2
[libgomp, testsuite, nvptx] Fix pr96390.c without CUDA
When running the libgomp testsuite on x86_64 with nvptx accelerator, we run into: ... XPASS: libgomp.c/../libgomp.c-c++-common/pr96390.c (test for excess errors) FAIL: libgomp.c/../libgomp.c-c++-common/pr96390.c execution test ... The problem is that we're expecting the following ptxas error: ... XFAIL: libgomp.c/../libgomp.c-c++-common/pr96390.c (test for excess errors) Excess errors: ptxas /tmp/ccZYDw8N.o, line 90; error : Call to 'baz' requires call prototype ptxas /tmp/ccZYDw8N.o, line 90; error : Unknown symbol 'baz' ... But it's not triggered because ptxas is not in the path, so nvptx-none-as defaults to --no-verify. So instead, we run into the same error at execution time. Fix this by forcing verification using: ... /* { dg-additional-options "-foffload=-Wa,--verify" \ { target offload_target_nvptx } } */ ... such that we run into the xfail in this way instead: ... XFAIL: libgomp.c/../libgomp.c-c++-common/pr96390.c (test for excess errors) Excess errors: nvptx-as: error trying to exec 'ptxas': execvp: No such file or directory nvptx-as: ptxas returned 255 exit status ... Tested on x86_64-linux with nvptx accelerator. libgomp/ChangeLog: 2022-02-21 Tom de Vries <tdevries@suse.de> PR testsuite/104146 * testsuite/libgomp.c++/pr96390.C: Add additional-option -foffload=-Wa,--verify for nvptx. * testsuite/libgomp.c-c++-common/pr96390.c: Same.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions