Hi!
On 2023-06-14T11:42:22+0200, Tobias Burnus wrote:
> On 14.06.23 10:09, Thomas Schwinge wrote:
>> Let me know if I should also adjust the new 'target { ! offload_device }'
>> diagnostic "[...] MANDATORY but only the host device is available" to
>> include a comma before 'but', for consistency
On 14.06.23 10:09, Thomas Schwinge wrote:
This reminds me of the (unresolved)https://gcc.gnu.org/PR81886
"Means to determine at runtime foffload targets specified at compile time".
I think there is the problem that we also support offloading in
libraries. Thus, if you compile the main program w
Hi!
On 2023-06-13T20:44:39+0200, Tobias Burnus wrote:
> I intent to commit this tomorrow, unless there are comments.
I'm sorry I'm late. ;-P
> It does as it says (see commit log): It initializes default-device-var
> to the value using the algorithm described in OpenMP 5.2, which
> depends on w
I intent to commit this tomorrow, unless there are comments.
It does as it says (see commit log): It initializes default-device-var
to the value using the algorithm described in OpenMP 5.2, which
depends on whether OMP_TARGET_OFFLOAD=mandatory was set.
NOTE: With -foffload=disable there is no bi
