https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121628
--- Comment #8 from anlauf at gcc dot gnu.org --- (In reply to Christopher Albert from comment #6) > (In reply to anlauf from comment #5) > > Created attachment 62363 [details] > > Slightly rewritten reproducer > > > > This slight rewrite might help pinning down where the memory corruption is > > happening. > > > > Thank for the follow-up! I posted a patch to gcc-patches with a fix: > https://gcc.gnu.org/pipermail/gcc-patches/2025-October/697921.html > > It involves both, compiler and runtime library changes, as this problem was > too hard to fix at the compilation stage alone. Happy if you could have a > look and tell me what you think. Thanks for working on the issue! Note that Fortran patches should also go to fortran@ so that developers take notice. Your patch does not apply here. Can you ensure that it applies to a clean trunk?
