qemu FTBFS with GCC 12
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc |
Fix Released
|
Medium
|
|||
gcc-12 (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
qemu (Ubuntu) |
Fix Released
|
High
|
Christian Ehrhardt |
Bug Description
qemu 1:7.0+dfsg-7ubuntu1 FTBFS on Kinetic due to an extra warning emitted by gcc 12:
----------------
In function ‘ppc64_
inlined from ‘cpu_970_init’ at /<<PKGBUILDDIR>
/<<PKGBUILDDIR>
400 | *dsi = 0x48002002;
| ~~~~~^~~~~~~~~~~~
/<<PKGBUILDDIR>
403 | *isi = 0x48002202;
| ~~~~~^~~~~~~~~~~~
[...]
cc1: all warnings being treated as errors
make[3]: *** [rules.mak:323: target/
----------------
Test rebuild done in this PPA:
https:/
Full build log:
Related branches
- git-ubuntu bot: Approve
- Andreas Hasenack: Approve
- Canonical Server Reporter: Pending requested
-
Diff: 6922 lines (+6313/-13)16 files modifieddebian/changelog (+4885/-3)
debian/control (+55/-8)
debian/control-in (+5/-2)
debian/patches/series (+6/-0)
debian/patches/ubuntu/define-ubuntu-machine-types.patch (+911/-0)
debian/patches/ubuntu/enable-svm-by-default.patch (+34/-0)
debian/patches/ubuntu/pre-bionic-256k-ipxe-efi-roms.patch (+62/-0)
debian/patches/ubuntu/qboot-Disable-LTO-for-ELF-binary-build-step.patch (+44/-0)
debian/qemu-block-extra.postinst (+59/-0)
debian/qemu-kvm-init (+89/-0)
debian/qemu-system-common.install (+1/-0)
debian/qemu-system-common.qemu-kvm.default (+8/-0)
debian/qemu-system-common.qemu-kvm.service (+16/-0)
debian/qemu-system-x86.NEWS (+80/-0)
debian/qemu-system-x86.README.Debian (+47/-0)
debian/rules (+11/-0)
- git-ubuntu bot: Approve
- Paride Legovini (community): Approve
- Canonical Server Reporter: Pending requested
-
Diff: 158 lines (+111/-1)5 files modifieddebian/changelog (+16/-0)
debian/patches/series (+2/-0)
debian/patches/ubuntu/lp1988710-opensbi-Makefile-fix-build-with-binutils-2.38.patch (+62/-0)
debian/patches/ubuntu/lp1988710-silence-openbios-array-bounds-false-positive.patch (+23/-0)
debian/rules (+8/-1)
Changed in qemu (Ubuntu): | |
importance: | Undecided → High |
tags: | added: rls-kk-incoming |
tags: | added: fr-2662 |
tags: |
added: foundations-todo removed: rls-kk-incoming |
Changed in gcc: | |
importance: | Unknown → Medium |
status: | Unknown → New |
tags: | added: server-todo |
Changed in qemu (Ubuntu): | |
assignee: | nobody → Christian Ehrhardt (paelzer) |
Changed in gcc: | |
status: | New → Confirmed |
tags: | removed: foundations-todo |
Changed in gcc-12 (Ubuntu): | |
importance: | Undecided → Medium |
tags: | removed: server-todo |
Changed in gcc: | |
status: | Confirmed → Fix Released |
Hmm,
0x48002002 < 0xFFFFFFFF
Is that a false positive or am I looking at the wrong target for this warning. /gcc.gnu. org/bugzilla/ show_bug. cgi?id= 101977 /gcc.gnu. org/bugzilla/ show_bug. cgi?id= 104657 /gcc.gnu. org/bugzilla/ show_bug. cgi?id= 99578
There are various reports about this and so far most I found where different kinds of false positives.
- https:/
- https:/
- https:/
If you consider this a false positive at the end of your check consider for now doing a wrapper with just this warning disabled on those two assignments:
#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Warray-bounds"
code
#pragma GCC diagnostic pop