This is the mail archive of the
mailing list for the GCC project.
Re: [patch, openmp/openacc] Allow Fortran parameters in map/copy.
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Andrew Stubbs <ams at codesourcery dot com>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Fortran List <fortran at gcc dot gnu dot org>
- Date: Fri, 5 Jul 2019 14:15:12 +0200
- Subject: Re: [patch, openmp/openacc] Allow Fortran parameters in map/copy.
- References: <email@example.com> <20190705114951.GL815@tucnak> <firstname.lastname@example.org>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Fri, Jul 05, 2019 at 01:10:00PM +0100, Andrew Stubbs wrote:
> > so I don't believe Fortran parameters are OpenMP variables.
> > Scalar Fortran parameters don't even have any data storage block associated
> > with them at all.
> Agreed, they are not variables (nor variable), and copying them about is
> entirely pointless (although, if you simply remove the error check GCC will
> happily create storage for 'N' and do the copies).
> And yet, this issue has generated a support request from a blocked customer,
> and I'd like to improve their experience.
> I could generate a warning, or add a note to the error message, but in the
> interests of portability I thought just doing the right thing would be
> Any suggestions?
I don't know what OpenACC says, perhaps it is different.
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.