diff options
| author | Laszlo Ersek <lersek@redhat.com> | 2017-08-15 18:09:57 +0200 |
|---|---|---|
| committer | Laszlo Ersek <lersek@redhat.com> | 2017-08-17 11:30:52 +0200 |
| commit | ca56256d5e0b7e63325b049e90a6bd03f90e3598 (patch) | |
| tree | 2b9fb77d4b3f5079dcf55c1760e9db4410484efe /OvmfPkg/build.sh | |
| parent | 5843dff25d7e74e0ddbd9528cc94b6c9fd8181cc (diff) | |
| download | edk2-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 'OvmfPkg/build.sh')
| -rwxr-xr-x | OvmfPkg/build.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/OvmfPkg/build.sh b/OvmfPkg/build.sh index 6821552025..5868d3b8c4 100755 --- a/OvmfPkg/build.sh +++ b/OvmfPkg/build.sh @@ -102,7 +102,7 @@ case `uname` in 4.8.*) TARGET_TOOLS=GCC48 ;; - 4.9.*|6.[0-2].*) + 4.9.*|6.[0-2].*|7.*) TARGET_TOOLS=GCC49 ;; *) |