From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Gao, Liming" <liming.gao@intel.com>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>,
"Shi, Steven" <steven.shi@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Laszlo Ersek <lersek@redhat.com>, Andrew Fish <afish@apple.com>,
"Ni, Ray" <ray.ni@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>,
"Feng, Bob C" <bob.c.feng@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [edk2-devel] [Patch 00/11] New Cross OS tool chain CLANG9
Date: Thu, 24 Oct 2019 01:44:50 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E521679@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <15CFFF4D1D17232C.6147@groups.io>
Push @d95de082da01f4a4cb3ebf87e15972a12d0f8d53..703232b8e8889e908771b64e22b5ed94e403aa0a
>-----Original Message-----
>From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
>Liming Gao
>Sent: Tuesday, October 22, 2019 10:44 PM
>To: devel@edk2.groups.io
>Cc: Yao, Jiewen <jiewen.yao@intel.com>; Shi, Steven
><steven.shi@intel.com>; Justen, Jordan L <jordan.l.justen@intel.com>; Laszlo
>Ersek <lersek@redhat.com>; Andrew Fish <afish@apple.com>; Ni, Ray
><ray.ni@intel.com>; Ard Biesheuvel <ard.biesheuvel@linaro.org>; Wang, Jian
>J <jian.j.wang@intel.com>; Wu, Hao A <hao.a.wu@intel.com>; Feng, Bob C
><bob.c.feng@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>;
>Leif Lindholm <leif.lindholm@linaro.org>
>Subject: [edk2-devel] [Patch 00/11] New Cross OS tool chain CLANG9
>
>In v4, use common GCC_ASM_FLAGS to replace GCC5_ASM_FLAGS.
>Update the fix in EmulatorPkg with WIN_HOST_BUILD flag.
>This version has got the review from all package maintainers.
>If no more comment, I will plan to push this patch set on Thursday 10-24.
>
>In v3, add the detail commit message for patch 3.
>Update the fix in EmulatorPkg based on the comments.
>
>In v2, drop patch 12, and update commit message for 5 & 11.
>
>BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1603
>Code: https://github.com/lgao4/edk2/tree/CLANG9_v4
>Wiki: https://github.com/lgao4/edk2/wiki/CLANG9-Tools-Chain
>
>CLANG9 tool chain is added to directly generate PE/COFF image (EFI image).
>This tool chain uses LLVM clang C compiler and lld linker, generates PE/COFF
>image and PDB compatible debug symbol format. Now, it supports IA32/X64
>Archs.
>It must use LLVM 9 or above release. LLVM 9 is ready on
>http://releases.llvm.org/download.html#9.0.0.
>
>CLANG9 is the cross OS tool chain. It can work on Windows/Linux/Mac host OS.
>For the same source code, with the same version LLVM tool chain,
>CLANG9 can generate the same binary image. So, the developer can
>choose the different development environment and work on the same
>code base. Besides, EDKII project build also requires third party
>tools: nasm and iasl. They both keep the same version. If so, the same
>binary image can be generated on the different host OS.
>
>LLVM tool chain provides the compiler and linker. To build EDK2 project,
>some other tools are still required. On Windows OS, nmake and Visual Studio
>are required to call Makefile and compile BaseTools C tools.
>On Linux/Mac, binutils and gcc are required to make and compile BaseTools
>C tools. Because VS or GCC are mainly used to compile BaseTools and provide
>nmake/make tool, they can keep on the stable version without update.
>
>To build source code, CLANG9 tool chain (-t CLANG9) can be specified
>on Windows OS, set CLANG_HOST_BIN=n, set CLANG9_BIN=LLVM installed
>directory
>CLANG_HOST_BIN is used CLANG_HOST_PREFIX. Prefix n is for nmake.
>For example:
>* set CLANG_HOST_BIN=n
>* set CLANG9_BIN=C:\Program Files\LLVM\bin\
>* set IASL_PREFIX=C:\Asl\
>
>On Linux/Mac, export CLANG9_BIN=LLVM installed directory,
>CLANG_HOST_BIN is
>not required, because there is no prefix for make.
>For example:
>* export CLANG9_BIN=/home/clang9/bin/
>
>Now, CLANG9 tool chain has been verified in Edk2 packages and
>Ovmf/Emulator
>with LLVM 9.0.0 on Windows and Linux OS.
>OVMF IA32/X64/IA32X64 all boots to Shell on Windows and Linux OS.
>Emulator can boot to Shell on Windows only with CLANG9.
>OVMF Ia32X64 RELEASE build generates the same BIOS images on Windows
>and Linux OS.
>
>Cc: Jiewen Yao <jiewen.yao@intel.com>
>Cc: Steven Shi <steven.shi@intel.com>
>Cc: Jordan Justen <jordan.l.justen@intel.com>
>Cc: Laszlo Ersek <lersek@redhat.com>
>Cc: Andrew Fish <afish@apple.com>
>Cc: Ray Ni <ray.ni@intel.com>
>Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>Cc: Jian J Wang <jian.j.wang@intel.com>
>Cc: Hao A Wu <hao.a.wu@intel.com>
>Cc: Bob Feng <bob.c.feng@intel.com>
>Cc: Michael D Kinney <michael.d.kinney@intel.com>
>Cc: Leif Lindholm <leif.lindholm@linaro.org>
>
>Liming Gao (11):
> BaseTools tools_def.template: Remove unnecessary $(DEST_DIR_DEBUG)
> path
> BaseTools tools_def: Add CLANG9 tool chain to directly generate PE
> image
> BaseTools GenFw: Fix the issue to update the wrong size as SectionSize
> MdePkg Base.h: Add definition for CLANG9 tool chain
> MdePkg BaseIoLibIntrinsic: Remove __inline__ attribute for IO
> functions
> MdeModulePkg LzmaCustomDecompressLib: Update macro to be same in
>CLANG
> tool
> MdeModulePkg RegularExpressionDxe: Disable warning for CLANG9 tool
> chain
> CryptoPkg: Append options to make CLANG9 tool chain pass build
> CryptoPkg IntrinsicLib: Make _fltused always be used
> EmulatorPkg: Enable CLANG9 tool chain
> OvmfPkg: Enable CLANG9 tool chain
>
> BaseTools/Source/C/GenFw/GenFw.c | 8 +-
> CryptoPkg/Library/IntrinsicLib/MemoryIntrinsics.c | 10 +-
> EmulatorPkg/Win/Host/WinHost.c | 6 +-
> MdePkg/Library/BaseIoLibIntrinsic/IoLibGcc.c | 6 -
> BaseTools/Conf/build_rule.template | 26 +++--
> BaseTools/Conf/tools_def.template | 124 +++++++++++++++++++--
> CryptoPkg/Library/BaseCryptLib/BaseCryptLib.inf | 1 +
> CryptoPkg/Library/BaseCryptLib/PeiCryptLib.inf | 1 +
> CryptoPkg/Library/BaseCryptLib/RuntimeCryptLib.inf | 1 +
> CryptoPkg/Library/BaseCryptLib/SmmCryptLib.inf | 1 +
> CryptoPkg/Library/OpensslLib/OpensslLib.inf | 1 +
> CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf | 1 +
> EmulatorPkg/EmulatorPkg.dsc | 14 ++-
> EmulatorPkg/Win/Host/WinHost.inf | 6 +
> .../LzmaCustomDecompressLib/Sdk/C/7zTypes.h | 2 +-
> .../RegularExpressionDxe/RegularExpressionDxe.inf | 3 +
> MdePkg/Include/Base.h | 6 +-
> MdePkg/Include/Ia32/ProcessorBind.h | 4 +-
> MdePkg/Include/X64/ProcessorBind.h | 2 +-
> OvmfPkg/OvmfPkgIa32.dsc | 4 +-
> OvmfPkg/OvmfPkgIa32X64.dsc | 4 +-
> OvmfPkg/OvmfPkgX64.dsc | 4 +-
> 22 files changed, 190 insertions(+), 45 deletions(-)
>
>--
>2.13.0.windows.1
>
>
>
parent reply other threads:[~2019-10-24 1:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <15CFFF4D1D17232C.6147@groups.io>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A89E2EF3DFEDB4C8BFDE51014F606A14E521679@SHSMSX104.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox