https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
--- Comment #5 from Tom de Vries ---
Created attachment 52438
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52438=edit
Tentative patch (GOMP_TARGET_ENV_ITER)
A more generic solution using env var GOMP_TARGET_ENV_ITER, which allows us to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
--- Comment #4 from Tom de Vries ---
Created attachment 52416
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52416=edit
[libgomp, testsuite, nvptx] Add GOMP_NVPTX_JIT_ITER (libgomp.c/c.exp only)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
--- Comment #3 from Tom de Vries ---
(In reply to Thomas Schwinge from comment #2)
> For OpenMP test cases, we'd either have to manually mark them up (error
> prone and generally ugly), or scan the source file(s) (error prone and
> generally
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
Thomas Schwinge changed:
What|Removed |Added
CC||tschwinge at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
--- Comment #1 from Tom de Vries ---
One of the dimensions that I test is env var GOMP_NVPTX_JIT, with values:
- -O0, and
- default (using unset GOMP_NVPTX_JIT), which supposedly is -O4.
Looking at f.i. test-case for-3.c, compilation takes 3
