Re: [PATCH] Fortran: fix front-end memleak after failure during parsing of NULLIFY

2025-03-01 Thread Harald Anlauf
Am 01.03.25 um 19:20 schrieb Steve Kargl: On Sat, Mar 01, 2025 at 03:56:21PM +0100, Harald Anlauf wrote: the attached patch fixes a front-end memleak that is seen when running f951 under valgrind and while parsing invalid uses of NULLIFY. I had this in my tree for some time without any problem

Re: [PATCH] Fortran: fix front-end memleak after failure during parsing of NULLIFY

2025-03-01 Thread Steve Kargl
On Sat, Mar 01, 2025 at 03:56:21PM +0100, Harald Anlauf wrote: > > the attached patch fixes a front-end memleak that is seen when > running f951 under valgrind and while parsing invalid uses of > NULLIFY. > > I had this in my tree for some time without any problems, in an > attempt to further red

[PATCH] Fortran: fix front-end memleak after failure during parsing of NULLIFY

2025-03-01 Thread Harald Anlauf
Dear all, the attached patch fixes a front-end memleak that is seen when running f951 under valgrind and while parsing invalid uses of NULLIFY. I had this in my tree for some time without any problems, in an attempt to further reduce leaks that obscure more significant front-end issues, but am o

Re: [Fortran, Patch, PR118747, v1] Prevent double free alloc. comp. in derived type function results

2025-03-01 Thread Paul Richard Thomas
Hi Andre, This looks fine to me. You say that this is a regression. How far back does it go? OK for mainline and, if required, for backporting. Thanks for the patch. Paul On Fri, 28 Feb 2025 at 15:54, Andre Vehreschild wrote: > Hi all, > > on this regression I had to chew a longer time. Ass