Shell/hexedit/libMemImage.c | 4 4 + 0 - 0 !
Shell/shellenv/cmddisp.c | 2 2 + 0 - 0 !
Shell/shellenv/echo.c | 1 1 + 0 - 0 !
Shell/shellenv/shelle.h | 1 1 + 0 - 0 !
4 files changed, 8 insertions(+)

 correct mismatched use of efiapi in efi shell code
 The EFIAPI define is not a no-op in GCC; it needs to be used consistently
 for both the prototype and the definition.

OvmfPkg/OvmfPkgIa32.dsc | 5 5 + 0 - 0 !
OvmfPkg/OvmfPkgIa32.fdf | 5 5 + 0 - 0 !
OvmfPkg/OvmfPkgIa32X64.dsc | 5 5 + 0 - 0 !
OvmfPkg/OvmfPkgIa32X64.fdf | 5 5 + 0 - 0 !
OvmfPkg/OvmfPkgX64.dsc | 5 5 + 0 - 0 !
OvmfPkg/OvmfPkgX64.fdf | 5 5 + 0 - 0 !
6 files changed, 30 insertions(+)

 enable the nvme driver
 Enable the driver for NVMe disks, not enabled by default upstream.
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1267816

BaseTools/Scripts/gcc4.4-ld-script | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 update linker script for gcc-4.9 which uses 64 byte alignment
 When the Facp.dll file is built w/ gcc-4.9, it uses a 64-byte alignment for
 the data section - but the EDK2 uses a linker script that only requires 32-
 byte alignment. This results in a binary that violates the ELF spec. GenFw
 has an assertion to catch this when doing a binary conversion - this trips,
 and the build fails.
 .
 This was resolved upstream by adding a new toolchain config for GCC49, which
 includes a new linker script that uses 64-byte alignment. This is a more
 surgical fix that just adjusts the existing GCC44 toolchain config (which is
 what we're using in Debian, even with gcc-4.9) to allow for 64-byte alignment.

BaseTools/Source/C/VfrCompile/VfrCompiler.cpp | 2 2 + 0 - 0 !
BaseTools/Source/C/VfrCompile/VfrCompiler.h | 3 2 + 1 - 0 !
2 files changed, 4 insertions(+), 1 deletion(-)

 fix undefined behavior in vfrcompiler.