Re: Handling of large stack objects in GPU code generation -- maybe transform into heap allocation?

2022-11-11 Thread Janne Blomqvist via Gcc
On Fri, Nov 11, 2022 at 4:13 PM Thomas Schwinge wrote: > For example, for Fortran code like: > > write (*,*) "Hello world" > > ..., 'gfortran' creates: > The issue: the stack object 'dt_parm.0' is a half-KiB in size (yes, > really! -- there's a lot of state in Fortran I/O apparently). > Any

Re: Handling of large stack objects in GPU code generation -- maybe transform into heap allocation?

2022-11-11 Thread Richard Biener via Gcc
On Fri, Nov 11, 2022 at 3:13 PM Thomas Schwinge wrote: > > Hi! > > For example, for Fortran code like: > > write (*,*) "Hello world" > > ..., 'gfortran' creates: > > struct __st_parameter_dt dt_parm.0; > > try > { > dt_parm.0.common.filename = > &"source-gcc/libgomp/test

Handling of large stack objects in GPU code generation -- maybe transform into heap allocation?

2022-11-11 Thread Thomas Schwinge
Hi! For example, for Fortran code like: write (*,*) "Hello world" ..., 'gfortran' creates: struct __st_parameter_dt dt_parm.0; try { dt_parm.0.common.filename = &"source-gcc/libgomp/testsuite/libgomp.oacc-fortran/print-1_.f90"[1]{lb: 1 sz: 1}; dt_parm.0.comm