[patch, openmp/openacc] Allow Fortran parameters in map/copy.

Andrew Stubbs ams@codesourcery.com
Fri Jul 5 14:49:00 GMT 2019


On 05/07/2019 15:04, Jakub Jelinek wrote:
>> For OpenMP, a warning is not good enough, because if Fortran PARAMETER is
>> not a variable, then the program is invalid and needs to be rejected.
>> You could improve the diagnostics by adding some explanation message that fortran
>> PARAMETER is not a variable.
> 
> Got it confirmed, it might change in a future OpenMP release; and there has
> been a change already in OpenMP 3.1 that might have intended to allow
> Fortran PARAMETERs in firstprivate clause, but because the glossary hasn't
> been changed, it is not valid even in firstprivate clause.

OK, here is an alternative patch that merely tries to make the error 
message more informative.

Basically, the user needs to get past "it isn't working but I need that 
value in this kernel", so hopefully this will help get them there.

WDYT?

Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 190705-map-parameters-2.patch
Type: text/x-patch
Size: 1676 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20190705/544e066b/attachment.bin>


More information about the Gcc-patches mailing list