https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123947
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
Last reconfirmed| |2026-02-26
--- Comment #11 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Curiously, the test cases in the attached patch and the original posted pass on
current trunk.
Also the testcase 0583_0023.f90 given in Comment #5 compiles and runs
correctly.
I also tested that with valgrind and it is clean:
$ valgrind ./a.out
==1010916== Memcheck, a memory error detector
==1010916== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
==1010916== Using Valgrind-3.26.0 and LibVEX; rerun with -h for copyright info
==1010916== Command: ./a.out
==1010916==
PASS
==1010916==
==1010916== HEAP SUMMARY:
==1010916== in use at exit: 0 bytes in 0 blocks
==1010916== total heap usage: 45 allocs, 45 frees, 9,636 bytes allocated
==1010916==
==1010916== All heap blocks were freed -- no leaks are possible
==1010916==
==1010916== For lists of detected and suppressed errors, rerun with: -s
==1010916== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
I am pretty sure this was fixed by the commit for PR124235 which I committed
earlier today. We call that a twofer.
I think I will add the additional testcases to the testsuite and regression
test to be sure.
