Re: [patch, fortran] Move some array packing to front end

Hi, I just compiled gcc-trunk after applying your patches (p8.diff) and H.J. Lu's patches from *Bug 88713* (vectorized code slow vs Flang) fixing rsqrt. Thomas Koenig already confirmed it fixed the problem I recorded there, but figured I'd add

Re: [patch, fortran] Move some array packing to front end

On Wed, Jan 23, 2019 at 6:18 PM Thomas Koenig wrote: > > Hi Dominique, > > > FAIL: gfortran.dg/internal_pack_4.f90 -O3 -fomit-frame-pointer > > -funroll-loops -fpeel-loops -ftracer -finline-functions execution test > > > > with -m32. > > > > gfc

Re: [patch, fortran] Move some array packing to front end

Hi, for the record, the attached version of the patch regtests cleanly and also passes the test that Dominique pointed out. I will defer this until stage 1 reopens. Regards Thomas Index: fortran/expr.c === ---

Re: [patch, fortran] Move some array packing to front end

Hi Dominique, FAIL: gfortran.dg/internal_pack_4.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test with -m32. gfc /opt/gcc/work/gcc/testsuite/gfortran.dg/internal_pack_4.f90 -O3 -funroll-loops -ftracer -m32 is enough to trigger the

Re: [patch, fortran] Move some array packing to front end

Hi Thomas, With your patch I see FAIL: gfortran.dg/internal_pack_4.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test with -m32. gfc /opt/gcc/work/gcc/testsuite/gfortran.dg/internal_pack_4.f90 -O3 -funroll-loops -ftracer -m32 is enough to

Re: [patch, fortran] Move some array packing to front end

On Tue, Jan 22, 2019 at 9:59 PM Thomas Koenig wrote: > > Hello world, > > the attached patch moves the packing / unpacking of arrays to the front > end when optimizing, but not for size. > > Rationale: internal_pack and internal_unpack are opaque to the compiler. > This can lead to a lot of

[patch, fortran] Move some array packing to front end

Hello world, the attached patch moves the packing / unpacking of arrays to the front end when optimizing, but not for size. Rationale: internal_pack and internal_unpack are opaque to the compiler. This can lead to a lot of information loss for inlining and inter- procedural optimization, and in