[Bug 1886155] [NEW] error: argument 2 of ‘__atomic_load’ discards ‘const’ qualifier

2020-07-03 Thread Martin Liska
Public bug reported: GCC 11 reports the following errors: [ 125s] In file included from /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/seqlock.h:17, [ 125s] from /home/abuild/rpmbuild/BUILD/qemu-5.0.0/include/qemu/qht.h:10, [ 125s] from /home/abuild/rp

[Bug 1874073] Re: openrisc_sim.c:87:42: error: 'cpu_irqs[0]' may be used uninitialized in this function [-Werror=maybe-uninitialized]

2020-05-27 Thread Martin Liska
Hello. The assert approach is preferred. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1874073 Title: openrisc_sim.c:87:42: error: 'cpu_irqs[0]' may be used uninitialized in this function [-Werro

[Bug 1874073] Re: openrisc_sim.c:87:42: error: 'cpu_irqs[0]' may be used uninitialized in this function [-Werror=maybe-uninitialized]

2020-04-21 Thread Martin Liska
Note that our -Wmaybe-uninitialized warnings tends to report false positives. We have a rich meta bug for it: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 That's why it can't prove the variable is initialized in all possible execution paths. ** Bug watch added: GCC Bugzilla #24639 https

[Bug 1874073] Re: openrisc_sim.c:87:42: error: 'cpu_irqs[0]' may be used uninitialized in this function [-Werror=maybe-uninitialized]

2020-04-21 Thread Martin Liska
Suggested patch: diff --git a/hw/openrisc/openrisc_sim.c b/hw/openrisc/openrisc_sim.c index 79e7049..724dcd0 100644 --- a/hw/openrisc/openrisc_sim.c +++ b/hw/openrisc/openrisc_sim.c @@ -129,7 +129,7 @@ static void openrisc_sim_init(MachineState *machine) const char *kernel_filename = machine-

[Bug 1874073] [NEW] openrisc_sim.c:87:42: error: 'cpu_irqs[0]' may be used uninitialized in this function [-Werror=maybe-uninitialized]

2020-04-21 Thread Martin Liska
Public bug reported: I see the warning since gcc10: static void openrisc_sim_init(MachineState *machine): ... qemu_irq *cpu_irqs[2]; ... serial_mm_init(get_system_memory(), 0x9000, 0, serial_irq, 115200, serial_hd(0), DEVICE_NATIVE_ENDIAN); I would initialize cpu

[Qemu-devel] [Bug 1801073] Re: util/zbin.c:390:37: error: absolute value function 'abs' given an argument of type 'long int' but has parameter of type 'int' which may cause truncation of value [-Werro

2019-01-21 Thread Martin Liska
Should be fixed here: http://git.ipxe.org/ipxe.git/commitdiff/956f6a722 Btw. how do you pull changes from ipxe into qemu repo? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1801073 Title: util/zbi

[Qemu-devel] [Bug 1801073] Re: util/zbin.c:390:37: error: absolute value function 'abs' given an argument of type 'long int' but has parameter of type 'int' which may cause truncation of value [-Werro

2019-01-21 Thread Martin Liska
Thank you, I contacted IPXE folks. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1801073 Title: util/zbin.c:390:37: error: absolute value function 'abs' given an argument of type 'long int' but h

[Qemu-devel] [Bug 1801073] [NEW] util/zbin.c:390:37: error: absolute value function 'abs' given an argument of type 'long int' but has parameter of type 'int' which may cause truncation of value [-Wer

2018-11-01 Thread Martin Liska
Public bug reported: For qemu-3.0.0 I see with GCC 9 compiler a new warning: $ make -j1 -C roms pxerom VERBOSE=1 V=1 make: Entering directory '/home/abuild/rpmbuild/BUILD/qemu-3.0.0/roms' make -C ipxe/src CONFIG=qemu \ PACKAGING_TIMESTAMP=1534273834 \ CROSS_COMPILE= \ bin/