blob: 26a40a5742a1068f874d69aa524aed8266532386 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
device: 0.900
permissions: 0.793
graphic: 0.768
PID: 0.591
vnc: 0.574
performance: 0.566
semantic: 0.519
socket: 0.490
files: 0.457
network: 0.356
boot: 0.300
debug: 0.232
other: 0.222
KVM: 0.021
qos-test fails when built with LTO and gcc-12
Description of problem:
The issue is already discussed here [1]. I'm simply building latest QEMU release and running the test suite. I thought the issue was fixed in 7.0 but it has resurfaced. Do QEMU dev's not build with LTO? I'm not able to debug this but I can test any proposed fixes etc. Thanks.
[1] https://lore.kernel.org/all/1d3bbff9e92e7c8a24db9e140dcf3f428c2df103.camel@suse.com/
Steps to reproduce:
1. Build QEMU with gcc-12 and LTO enabled
2. Run make check
3. Observe test suite failures in qos-test
Additional information:
```
Summary of Failures:
2/265 qemu:qtest+qtest-aarch64 / qtest-aarch64/qos-test ERROR 0.59s killed by signal 6 SIGABRT
3/265 qemu:qtest+qtest-i386 / qtest-i386/qos-test ERROR 0.22s killed by signal 6 SIGABRT
7/265 qemu:qtest+qtest-x86_64 / qtest-x86_64/qos-test ERROR 0.40s killed by signal 6 SIGABRT
```
|