[Bug 1994020] Re: SRU: update gcc-9 (PR105162) and gcc-10 to the final 10.5.0 release

[Robby Pocase]

@Matthias Klose  I see that gcc 10.5 made it into updates in the last
couple days. It's unclear to me based on affected release status if the
gcc-9 PR cherry pick is planned for SRU. Could you share the plans
around this?

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

Title:
  SRU: update gcc-9 (PR105162) and gcc-10 to the final 10.5.0 release

Status in gcc-10 package in Ubuntu:
  Invalid
Status in gcc-10-cross package in Ubuntu:
  Invalid
Status in gcc-10-cross-mipsen package in Ubuntu:
  New
Status in gcc-10-cross-ports package in Ubuntu:
  Invalid
Status in gcc-9 package in Ubuntu:
  Invalid
Status in gcc-9-cross package in Ubuntu:
  Invalid
Status in gcc-9-cross-ports package in Ubuntu:
  Invalid
Status in gcc-10 source package in Focal:
  Triaged
Status in gcc-10-cross source package in Focal:
  Fix Released
Status in gcc-10-cross-mipsen source package in Focal:
  Fix Released
Status in gcc-10-cross-ports source package in Focal:
  Fix Released
Status in gcc-9 source package in Focal:
  Triaged
Status in gcc-9-cross source package in Focal:
  Triaged

Bug description:
  SRU: update gcc-9 (PR105162) and gcc-10 to the final 10.5.0 release

  update 20.04 LTS to the final gcc-10 10.5.0 release.

  The GCC testsuite itself doesn't show regressions.

  A test-rebuild of focal/main with updated gcc-9 and gcc-10 packages
  was done to check for regressions:

  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230629-focal-focal.html
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230629-focal-gcc-focal.html

  The gcc-9 update is just a cherry pick of PR 105162 (arm64 specific).
  Test included in the GCC tests.

  The gcc-10 packages were done with the GCC 10.5.0 release candidate,
  and later updated to the final 10.5.0 release. The only change besides
  the version number is a bug fix in the D frontend.

  The GCC testsuites don't show regressions.

  There is one regression, dee on riscv64, timing out on the buildd in
  the testsuite. Newer uploads of the dee package have the testsuite
  disabled on riscv64, so apparently a known issue. We can backport that
  fix, if wanted.

  There are a few progressions: mir, python-openstacksdk, swift,
  udisks2, all riscv64 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1994020/+subscriptions