public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ray" <ray.ni@intel.com>
To: gaoliming <gaoliming@byosoft.com.cn>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH 0/6] Add CLANGDWARF toolchain for universal payload needs
Date: Thu, 3 Jun 2021 06:08:49 +0000	[thread overview]
Message-ID: <CO1PR11MB4930D5D430C42ACB8ED661248C3C9@CO1PR11MB4930.namprd11.prod.outlook.com> (raw)
In-Reply-To: <008801d75816$3fa80620$bef81260$@byosoft.com.cn>

Liming,
I resent the V2 that removed the conflict messages and corrected your mail address.
I am using CLANG V11.
https://bugzilla.tianocore.org/show_bug.cgi?id=3431 was submitted.

Thanks,
Ray

> -----Original Message-----
> From: gaoliming <gaoliming@byosoft.com.cn>
> Sent: Thursday, June 3, 2021 9:18 AM
> To: devel@edk2.groups.io; Ni, Ray <ray.ni@intel.com>
> Subject: 回复: [edk2-devel] [PATCH 0/6] Add CLANGDWARF toolchain for universal payload needs
> 
> Ray:
>   Thanks for your effort to integrate CLANGDWARF tool chain. Previous work
> bases on CLANG8. Now, which version CLANG compiler is used?
> 
>   And, can you submit one BZ for this new feature? Then, I can add it to the
> feature planning.
> 
>   Besides, please remove conflict message in the commit message of patch
> 2~4.
> 
> Thanks
> Liming
> > -----邮件原件-----
> > 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Ni, Ray
> > 发送时间: 2021年6月2日 15:46
> > 收件人: devel@edk2.groups.io
> > 主题: [edk2-devel] [PATCH 0/6] Add CLANGDWARF toolchain for universal
> > payload needs
> >
> > Universal payload requires its format in ELF format while today's EDKII
> > doesn't contain a cross OS toolchain that generates ELF images.
> >
> > The patch set is based on Liming's work in year 2019 and some very minor
> > modifications are made:
> > 1. Update toolchain name from CLANG8ELF to CLANGDWARF.
> > 2. Update link script to keep dynamic section.
> >
> > Liming Gao (4):
> >   BaseTools: Add ClangBase.lds for CLANG8 tool chain with max-page-size
> >   BaseTools GenFw: Support CLANG8ELF with conversion ELF to PE/COFF
> >     image
> >   BaseTools: Update build_rule to skip CLANG resource section generation
> >   BaseTools: Add new CLANG8ELF tool chain for new LLVM/CLANG8
> >
> > Ray Ni (2):
> >   BaseTools: Update ClangBase.lds to keep dynamic section
> >   BaseTools: Change CLANG8ELF to CLANGDWARF
> >
> >  BaseTools/Conf/build_rule.template      |   5 +-
> >  BaseTools/Conf/tools_def.template       | 109
> > +++++++++++++++++++++++-
> >  BaseTools/Scripts/ClangBase.lds         |  78 +++++++++++++++++
> >  BaseTools/Source/C/GenFw/Elf32Convert.c |  12 +--
> >  BaseTools/Source/C/GenFw/Elf64Convert.c |   5 +-
> >  5 files changed, 192 insertions(+), 17 deletions(-)
> >  create mode 100644 BaseTools/Scripts/ClangBase.lds
> >
> > --
> > 2.31.1.windows.1
> >
> >
> >
> > 
> >
> 
> 


  reply	other threads:[~2021-06-03  6:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  7:45 [PATCH 0/6] Add CLANGDWARF toolchain for universal payload needs Ni, Ray
2021-06-02  7:45 ` [PATCH 1/6] BaseTools: Add ClangBase.lds for CLANG8 tool chain with max-page-size Ni, Ray
2021-06-02  7:45 ` [PATCH 2/6] BaseTools GenFw: Support CLANG8ELF with conversion ELF to PE/COFF image Ni, Ray
2021-06-02  7:45 ` [PATCH 3/6] BaseTools: Update build_rule to skip CLANG resource section generation Ni, Ray
2021-06-02  7:45 ` [PATCH 4/6] BaseTools: Add new CLANG8ELF tool chain for new LLVM/CLANG8 Ni, Ray
2021-06-02  7:45 ` [PATCH 5/6] BaseTools: Update ClangBase.lds to keep dynamic section Ni, Ray
2021-06-02  7:45 ` [PATCH 6/6] BaseTools: Change CLANG8ELF to CLANGDWARF Ni, Ray
2021-06-03  1:17 ` 回复: [edk2-devel] [PATCH 0/6] Add CLANGDWARF toolchain for universal payload needs gaoliming
2021-06-03  6:08   ` Ni, Ray [this message]
2021-06-03  6:09     ` Ni, Ray

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=CO1PR11MB4930D5D430C42ACB8ED661248C3C9@CO1PR11MB4930.namprd11.prod.outlook.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