summaryrefslogtreecommitdiffstats
path: root/BaseTools/Source/Python/Ecc/MetaFileWorkspace
diff options
context:
space:
mode:
authorLaszlo Ersek <lersek@redhat.com>2017-08-15 18:09:57 +0200
committerLaszlo Ersek <lersek@redhat.com>2017-08-17 11:30:52 +0200
commitca56256d5e0b7e63325b049e90a6bd03f90e3598 (patch)
tree2b9fb77d4b3f5079dcf55c1760e9db4410484efe /BaseTools/Source/Python/Ecc/MetaFileWorkspace
parent5843dff25d7e74e0ddbd9528cc94b6c9fd8181cc (diff)
downloadedk2-ca56256d5e0b7e63325b049e90a6bd03f90e3598.tar.gz
edk2-ca56256d5e0b7e63325b049e90a6bd03f90e3598.tar.bz2
edk2-ca56256d5e0b7e63325b049e90a6bd03f90e3598.zip
OvmfPkg/build.sh: select the GCC49 toolchain settings for gcc-7.*
When UefiCpuPkg/MpInitLib is built for X64 with gcc-7, using the DEBUG build target and the GCC5 toolchain settings, a C-language assignment is miscompiled such that the initial AP startup hangs in CpuMpPei (X64) or CpuDxe (Ia32X64). See <https://bugzilla.tianocore.org/show_bug.cgi?id=671> for a detailed analysis of the symptoms, and for mailing list links. This issue has been reported several times (one example is <https://bugzilla.tianocore.org/show_bug.cgi?id=657>). Until we (or the upstream gcc developers) figure out how to dissuade gcc-7 from the miscompilation, pick the GCC49 toolchain in "build.sh" for gcc-7.*. Cc: Alex Williamson <alex.williamson@redhat.com> Cc: Jordan Justen <jordan.l.justen@intel.com> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Laszlo Ersek <lersek@redhat.com> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/Ecc/MetaFileWorkspace')
0 files changed, 0 insertions, 0 deletions