As mentioned before - I didn't trust this result. And with "likeliness" of this being so low we all know that results are unreliable. Due to that now r10-6822 is
r10-6822 - bad 2 of 67 The signature was the same "add_regs_to_insn_regno_info (lra)" as before on (again) different places tcg/tcg.c:2180 and fpu/softfloat.c:7133. What to do from here ... We could bisect again starting with r10-6822 and 20190425 and use at least like 100 runs each. But that would be a last resort as I'm on ~1run/h which means ~4 days each step. I have a few "maybe we are lucky" things to try first: - 10.2.1-1 in hirsute - trunk gcc-r11-5879.tar.xz - Doing a run with -O1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890435 Title: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/groovy/+bug/1890435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
