https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84779
--- Comment #20 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- (In reply to Christopher Albert from comment #19) --- snip --- > On which machine are you testing this and what exactly does produce this > error? I could not reproduce any valgrind problem here. > > - GCC: 16.0.1 20260318 (experimental), r16-9623-g110a8007906 > - System: Linux 6.19.7-1-cachyos x86_64 > - Valgrind: 3.25.1 $ valgrind /path/to/install/libexec/gcc/x86_64-pc-linux-gnu/16.0.1/f951 pr84779.f90 --- snip --- Extra diagnostic checks enabled; compiler may run slowly. Configure with --enable-checking=release to disable checks. ==622618== ==622618== HEAP SUMMARY: ==622618== in use at exit: 1,425,443 bytes in 1,113 blocks ==622618== total heap usage: 12,373 allocs, 11,260 frees, 4,029,222 bytes allocated ==622618== ==622618== LEAK SUMMARY: ==622618== definitely lost: 0 bytes in 0 blocks ==622618== indirectly lost: 0 bytes in 0 blocks ==622618== possibly lost: 0 bytes in 0 blocks ==622618== still reachable: 1,425,443 bytes in 1,113 blocks ==622618== suppressed: 0 bytes in 0 blocks ==622618== Rerun with --leak-check=full to see details of leaked memory ==622618== ==622618== Use --track-origins=yes to see where uninitialised values come from ==622618== For lists of detected and suppressed errors, rerun with: -s ==622618== ERROR SUMMARY: 336 errors from 26 contexts (suppressed: 0 from 0) Using: valgrind-3.26.0 gcc version 16.0.1 20260316 Linux 6.19.8-200.fc43.x86_64
