https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77493
--- Comment #5 from David Abdurachmanov <david.abdurachmanov at gmail dot com> --- I tried running valgrind on both x86_64 and ppc64le. It was running for 2 days and didn't report any invalid reads / writes to the memory. My first guess was that we are corrupting memory. I added -g -fsanitize=undefined -fno-omit-frame-pointer [-static-libubsan] on involved pieces and it did produce some errors. None of that seems to touch troublesome part of code, but with these flags code works again. So far I am running builds with -fno-crossjumping and that seems to solve all issues. Also, trying to bring back ASan builds, but that will take time thus I will keep looking into this.
