This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libgomp/81886] Means to determine at runtime foffload targets specified at compile time


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81886

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)

These are all related to timing issues. Maybe not related to the patch.

> FAIL: libgomp.oacc-c-c++-common/lib-74.c -foffload=nvptx-none  -O0 
> execution test
> FAIL: libgomp.oacc-c-c++-common/lib-74.c -foffload=nvptx-none  -O2 
> execution test

'./lib-74.exe'; echo XYZ$?ZYX^M
actual time < delay time^M
Aborted (core dumped)^M

> FAIL: libgomp.oacc-c-c++-common/lib-78.c -foffload=nvptx-none  -O0 
> execution test
> FAIL: libgomp.oacc-c-c++-common/lib-78.c -foffload=nvptx-none  -O2 
> execution test

'./lib-78.exe'; echo XYZ$?ZYX^M
actual time < delay time^M
Aborted (core dumped)^M

> FAIL: libgomp.oacc-c-c++-common/lib-83.c -foffload=nvptx-none  -O0 
> execution test
> FAIL: libgomp.oacc-c-c++-common/lib-83.c -foffload=nvptx-none  -O2 
> execution test

'./lib-83.exe'; echo XYZ$?ZYX^M
actual time too long^M
Aborted (core dumped)^M

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]