> On Wed, Aug 1, 2012 at 3:13 AM, <g...@mprc.pku.edu.cn> wrote: >> are available in the git repository at: >> >> git://github.com/gxt/QEMU.git unicore32 > > I'm still getting these errors, please fix: > CC libhw32/hw/puv3_gpio.o > /src/qemu/hw/puv3_gpio.c: In function 'puv3_gpio_read': > /src/qemu/hw/puv3_gpio.c:48:5: error: 'ret' may be used uninitialized > in this function [-Werror=maybe-uninitialized] > cc1: all warnings being treated as errors > make[1]: *** [hw/puv3_gpio.o] Error 1 > CC libhw32/hw/puv3_pm.o > /src/qemu/hw/puv3_pm.c: In function 'puv3_pm_read': > /src/qemu/hw/puv3_pm.c:74:5: error: 'ret' may be used uninitialized in > this function [-Werror=maybe-uninitialized] > cc1: all warnings being treated as errors > make[1]: *** [hw/puv3_pm.o] Error 1 > CC libhw32/hw/puv3_dma.o > /src/qemu/hw/puv3_dma.c: In function 'puv3_dma_read': > /src/qemu/hw/puv3_dma.c:44:5: error: 'ret' may be used uninitialized > in this function [-Werror=maybe-uninitialized] > cc1: all warnings being treated as errors >
Thanks Blue. I can't get these errors in my server. Perhaps gcc versions are different, and my gcc is 4.4.3. Maybe, new gcc check each branch of switch statement? I will correct these errors, and resend the patch series. Besides, because openrisc32 had been merged into qemu, I need adjust the value of QEMU_ARCH_UNICORE32. Is 0x4000 proper? Or it has to be 16384? Thanks & Regards, Guan Xuetao