https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123299
Bug ID: 123299
Summary: c-c++-common/gomp/uses_allocators-8.c is UNRESOLVED
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: burnus at gcc dot gnu.org
Target Milestone: ---
The new c-c++-common/gomp/uses_allocators-8.c test is UNRESOLVED (apparently
everywhere):
+UNRESOLVED: c-c++-common/gomp/uses_allocators-8.c -std=c++20 scan-tree-dump
original "#pragma omp target uses_allocators\\\\(memspace\\\\(1\\\\),
traits\\\\(\\\\) : my4\\\\) uses_allocators\\\\(memspace\\\\(\\\\),
traits\\\\(t2\\\\) : my3\\\\) uses_allocators\\\\(memspace\\\\(\\\\),
traits\\\\(\\\\) : my2\\\\) uses_allocators\\\\(memspace\\\\(3\\\\),
traits\\\\(t\\\\) : my\\\\)"
+UNRESOLVED: c-c++-common/gomp/uses_allocators-8.c -std=c++26 scan-tree-dump
original "#pragma omp target uses_allocators\\\\(memspace\\\\(1\\\\),
traits\\\\(\\\\) : my4\\\\) uses_allocators\\\\(memspace\\\\(\\\\),
traits\\\\(t2\\\\) : my3\\\\) uses_allocators\\\\(memspace\\\\(\\\\),
traits\\\\(\\\\) : my2\\\\) uses_allocators\\\\(memspace\\\\(3\\\\),
traits\\\\(t\\\\) : my\\\\)"
+UNRESOLVED: c-c++-common/gomp/uses_allocators-8.c -std=c++98 scan-tree-dump
original "#pragma omp target uses_allocators\\\\(memspace\\\\(1\\\\),
traits\\\\(\\\\) : my4\\\\) uses_allocators\\\\(memspace\\\\(\\\\),
traits\\\\(t2\\\\) : my3\\\\) uses_allocators\\\\(memspace\\\\(\\\\),
traits\\\\(\\\\) : my2\\\\) uses_allocators\\\\(memspace\\\\(3\\\\),
traits\\\\(t\\\\) : my\\\\)"
+UNRESOLVED: c-c++-common/gomp/uses_allocators-8.c scan-tree-dump original
"#pragma omp target uses_allocators\\\\(memspace\\\\(1\\\\), traits\\\\(\\\\) :
my4\\\\) uses_allocators\\\\(memspace\\\\(\\\\), traits\\\\(t2\\\\) : my3\\\\)
uses_allocators\\\\(memspace\\\\(\\\\), traits\\\\(\\\\) : my2\\\\)
uses_allocators\\\\(memspace\\\\(3\\\\), traits\\\\(t\\\\) : my\\\\)"
The log shows that compilation fails:
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/gomp/uses_allocators-8.c:
In function 'f':
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/gomp/uses_allocators-8.c:52:36:
sorry, unimplemented: 'uses_allocators' clause
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/gomp/uses_allocators-8.c:52:36:
sorry, unimplemented: 'uses_allocators' clause
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/gomp/uses_allocators-8.c:52:36:
sorry, unimplemented: 'uses_allocators' clause
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/gomp/uses_allocators-8.c:52:36:
sorry, unimplemented: 'uses_allocators' clause
compiler exited with status 1
thus the dump doesn't exist:
c-c++-common/gomp/uses_allocators-8.c: dump file does not exist
which turns the scan-tree-dump test UNRESOLVED.
This mistake is common, actually: just checking for FAILs isn't enough:
both UNRESOLVED and XPASS tests require attention. This can easily be avoided
by using the toplevel mail-report.log target: the resulting output highlights
just the problematic tests, so something like this isn't missed.
This failure creates lots of testsuite noise. It could be reduced a bit by
avoiding double quotes in the scan-tree-dump regex, but using braces instead.
This nicely avoids the excessive (and hard to read) \ escapes that are
otherwise
necessary.
