Re: [Fortran, Patch, PR120483, v2] Fix wrong type of saved allocatable strings.

Hi Harald, I don't think it is necessarily the save attribute, but rather it's representation in "assembler". To my understanding the type's size is needed to allocate space in the .RSS or .data segment of the binary. To manage this the size needs to be compile time computable, which it is not

Re: [PATCH] Fortran: ICE due to missing locus with data statement for coarray [PR99838]

Hi Andre, On 6/3/25 21:03, Andre Vehreschild wrote: Hi Harald, Lgtm. That patch is nearly obvious. Ok for trunk and backport. Thanks for the patch, Andre thanks for the swift review! Pushed as r16-1090-g0768ec0d32f570. Thanks, Harald Andre Vehreschild * ve...@gmx.de Am 3. Juni 2025 20:43

Re: [Fortran, Patch, PR120483, v2] Fix wrong type of saved allocatable strings.

Hi Andre, On 6/3/25 13:31, Andre Vehreschild wrote: Hi all, thanks for the explanations, Christophe. This is very much appreciated. And sorry, I can't follow all presentations, conferences and publications. There is meanwhile way too much for me to process out there. Anyway, the regression I p

Re: [PATCH] Fortran: ICE due to missing locus with data statement for coarray [PR99838]

Hi Harald, Lgtm. That patch is nearly obvious. Ok for trunk and backport. Thanks for the patch, Andre Andre Vehreschild * ve...@gmx.de Am 3. Juni 2025 20:43:52 schrieb Harald Anlauf : Dear all, here's a fix for another one of Gerhard's "torture tests" that triggers an ICE with -Warray-tempor

[PATCH] Fortran: ICE due to missing locus with data statement for coarray [PR99838]

Dear all, here's a fix for another one of Gerhard's "torture tests" that triggers an ICE with -Warray-temporaries. The cause was that the locus was not set for the initializer of the symbol for the testcase. The obvious fix is to then use the locus from the array constructor generated for the d

Re: [Fortran, Patch, PR120483, v2] Fix wrong type of saved allocatable strings.

Hi all, thanks for the explanations, Christophe. This is very much appreciated. And sorry, I can't follow all presentations, conferences and publications. There is meanwhile way too much for me to process out there. Anyway, the regression I produced in gomp should be fixed by the new version of p

Re: Execution time for gfortran regression testing

Le 30/05/2025 à 22:28, Harald Anlauf a écrit : When I'm working on a particular area of gfortran, I tend to use RUNTESTFLAGS to limit what is tested.  For example, I just fixed SPREAD() for scalar source and ncopies < 1. I do % cd obj % gmake % cd gcc % gmake check-fortran RUNTESTFLAGS="dg.exp=s

Re: [Fortran, Patch, PR120483, v1] Fix wrong type of saved allocatable strings.

Hi! On Mon, 2 Jun 2025 at 20:53, Andre Vehreschild wrote: > > Hi Thomas, > > thanks for the ok. Unfortunately does the patch regress in gomp (test case > gomp/pr104382 when I am not mistaken ; the one with the lone 'save' > statement). This was reported by the regression testing host at first