[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault

[Christian Ehrhardt ]

Fails with -O1 as well, although I have to admit that different -O
levels are deeply integrated in qemus build system. So it is hard to
overwrite "all of them". Therefore - while I set -O1 and that affected
some builds, it isn't implying that all compiler calls were -O1.

I know dannf has made some bare-metal tests and so far none of those have failed.
Unfortunately our builders are VM based, so that isn't very helpful anyway.
Never the less I've transported my test container over to a box to build there.

Trying to maas-deploy a few more chip types didn't work out, but maybe
it will eventually with some help by the HWE team.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-10 in Ubuntu.
https://bugs.launchpad.net/bugs/1890435

Title:
  gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation
  fault

Status in gcc:
  Confirmed
Status in gcc-10 package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  this could be the same as bug 1887557 but as I don't have enough data I'm filing it as individual issue for now.

  I have only seen this happening on armhf so far.
  In 2 of 5 groovy builds of qemu 5.0 this week I have hit the issue, but it is flaky.

  Flakyness:
  1. different file
  first occurrence
  /<<PKGBUILDDIR>>/target/s390x/excp_helper.c:544:1: internal compiler error: Segmentation fault
  second occurrence
  /<<PKGBUILDDIR>>/linux-user/syscall.c:12479:1: internal compiler error: Segmentation fault

  Being so unreliable I can't provide mcuh more yet.
  I filed it mostly for awareness and so that I can be dup'ed onto the right but if there is a better one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1890435/+subscriptions