[Xen-devel] [PATCH for-4.7 0/6] Workaround gcc -Wmaybe-uninitialised false positive reports

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On my Debian Jessie build box gcc complains about various maybe uninitialised
variables when -g is in use. In fact gcc -Wmaybe-uninitialized is not very
reliable according to gcc manpage, various search results and answer from
someone on freenode #gcc channel.

I go through those failures and try to provide some workaround for them.
Please have a look if these fixes make sense or my analysis is correct.

Wei.

Wei Liu (6):
  rombios/tcgbios: initialise size in tcpa_extend_acpi_log
  rombios/tcgbios: initialise entry in HashLogEvent32
  rombios/tcgbios: initialise logdataptr in HashLogEvent32
  blktap2: initialise buf in vhd_util_check_footer
  blktap2: initialise buf to NULL in img2qcow.c:main
  blktap2: initialise buf in qcow2raw.c:main

 tools/blktap2/drivers/img2qcow.c               | 2 +-
 tools/blktap2/drivers/qcow2raw.c               | 2 +-
 tools/blktap2/vhd/lib/vhd-util-check.c         | 2 +-
 tools/firmware/rombios/32bit/tcgbios/tcgbios.c | 6 +++---
 4 files changed, 6 insertions(+), 6 deletions(-)

-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel