aboutsummaryrefslogtreecommitdiff
path: root/gcc/fortran
diff options
context:
space:
mode:
authorTobias Burnus <tburnus@baylibre.com>2025-05-28 15:14:14 +0200
committerTobias Burnus <tburnus@baylibre.com>2025-05-28 15:14:14 +0200
commit5b2e7afb135aa10e17e51b891d4b2c85ee541ade (patch)
tree7642c89dba67d28faa302ae49a876515ef096825 /gcc/fortran
parent06b9c58c70a4fee7cc680aaeb5790aaadbb9fc77 (diff)
downloadgcc-5b2e7afb135aa10e17e51b891d4b2c85ee541ade.zip
gcc-5b2e7afb135aa10e17e51b891d4b2c85ee541ade.tar.gz
gcc-5b2e7afb135aa10e17e51b891d4b2c85ee541ade.tar.bz2
libgomp.fortran/metadirective-1.f90: Expect 'error:' for nvptx compile [PR118694]
This should have been part of commit r16-838-gb3d07ec7ac2ccd or r16-883-g5d6ed6d604ff94 - all showing the same issue: '!$omp target' followed by a metadirective with 'teams'; if the metadirective cannot be early resolved, a diagnostic error is shown about using directives between 'target' and 'teams'. While the message is misleading, the problem is that the host invokes 'target' differently when 'teams' is present; in this case, host fallback + amdgcn offload require the no-teams case, nvptx offload the teams case such that it only can be resolved at runtime. Mark the error as 'dg-bogus + xfail' to silence the FAIL, when nvptx offloading is compiled for. (If not, the metadirective can be resolved early during compilation.) libgomp/ChangeLog: PR middle-end/118694 * testsuite/libgomp.fortran/metadirective-1.f90: xfail when compiling (also) for nvptx offloading as an error is then expected.
Diffstat (limited to 'gcc/fortran')
0 files changed, 0 insertions, 0 deletions