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

2020-01-20 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81886 --- Comment #8 from Tobias Burnus --- Related: https://gcc.gnu.org/ml/gcc-patches/2020-01/msg01183.html (full thread) Namely, AMD GCN has different ISA – and depending which are available in the binary, the hardware could be chosen; having the w

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

2019-11-18 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81886 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org Bl

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

2017-08-30 Thread tschwinge at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81886 Thomas Schwinge changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

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

2017-08-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81886 --- Comment #5 from Tom de Vries --- AFAICT, this is the last version of the patch that was submitted: https://gcc.gnu.org/ml/gcc-patches/2015-10/msg01771.html

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

2017-08-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81886 --- Comment #4 from Tom de Vries --- (In reply to Tom de Vries from comment #2) > FAIL: libgomp.oacc-c-c++-common/parallel-dims.c -foffload=nvptx-none -O0 > (test for excess errors) > FAIL: libgomp.oacc-c-c++-common/parallel-dims.c -foffload=nv

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

2017-08-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81886 --- Comment #3 from Tom de Vries --- (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 > FAI

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

2017-08-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81886 --- Comment #2 from Tom de Vries --- Created attachment 42001 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42001&action=edit trunk patch This is a version of the patch for trunk. It introduces some failures for c and c++, but that might

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

2017-08-18 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81886 --- Comment #1 from Tom de Vries --- This is the initial commit to gomp-4_0-branch : https://gcc.gnu.org/ml/gcc-patches/2015-08/msg01264.html .