[Bug fortran/94358] [OMP] Privatize internal array variables introduced by the Fortran FE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94358 --- Comment #4 from Tobias Burnus --- (In reply to Tobias Burnus from comment #3) > And with optional there are additional issues – especially for > assumed-shape arrays as one has to check 'y == NULL' (argument absent) and > 'y->data == NULL'

[Bug fortran/94358] [OMP] Privatize internal array variables introduced by the Fortran FE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94358 --- Comment #3 from Tobias Burnus --- (In reply to Thomas Schwinge from comment #2) > Tobias, as a first step, can you please provide an exemplary Fortran test > case that shows some cases of what code the Fortran front end generates to >

[Bug fortran/94358] [OMP] Privatize internal array variables introduced by the Fortran FE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94358 --- Comment #2 from Thomas Schwinge --- (In reply to Thomas Schwinge from comment #0) > The original test case, 'gcc/testsuite/gfortran.dg/goacc/default_none.f95', > had already gotten committed (unmodified) to trunk in r229832 (commit >

[Bug fortran/94358] [OMP] Privatize internal array variables introduced by the Fortran FE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94358 --- Comment #1 from Thomas Schwinge --- To help with OpenACC 'kernels' support, Gergő later submitted for og8 an additional change in "Rework OpenACC Fortran DO loop

[Bug fortran/94358] [OMP] Privatize internal array variables introduced by the Fortran FE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94358 Thomas Schwinge changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |burnus at gcc dot gnu.org