SRU: update gcc-9 (PR105162) and gcc-10 to the final 10.5.0 release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc-10 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Unassigned | ||
gcc-10-cross (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Unassigned | ||
gcc-10-cross-mipsen (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
gcc-10-cross-ports (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Unassigned | ||
gcc-9 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Unassigned | ||
gcc-9-cross (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Unassigned | ||
gcc-9-cross-ports (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
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:/
https:/
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-
Changed in gcc-10 (Ubuntu): | |
status: | New → Invalid |
Changed in gcc-10 (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in gcc-10-cross (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Invalid |
Changed in gcc-10-cross (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in gcc-10-cross-ports (Ubuntu): | |
status: | New → Invalid |
Changed in gcc-10-cross-ports (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in gcc-9 (Ubuntu): | |
status: | New → Invalid |
Changed in gcc-9 (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in gcc-9-cross (Ubuntu): | |
status: | New → Invalid |
Changed in gcc-9-cross (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in gcc-9-cross-ports (Ubuntu): | |
status: | New → Invalid |
Changed in gcc-9-cross-ports (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | New → Triaged |
summary: |
- SRU: update gcc-9 (PR105162) and gcc-10 to the final 10.4.0 release + SRU: update gcc-9 (PR105162) and gcc-10 to the final 10.5.0 release |
description: | updated |
no longer affects: | gcc-9-cross-ports (Ubuntu Focal) |
description: | updated |
Changed in gcc-10 (Ubuntu Focal): | |
status: | Triaged → Fix Released |
Changed in gcc-10-cross-mipsen (Ubuntu): | |
status: | New → Invalid |
gcc-9 is at 9.5.0 and gcc-10 is at 10.4.0 on jammy updates. It seems only pending item would be to back both for Focal.