public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: edk2-devel@lists.01.org, liming.gao@intel.com,
	yonghong.zhu@intel.com, steven.shi@intel.com, evan.lloyd@arm.com,
	lersek@redhat.com
Subject: Re: [PATCH v3 0/3] BaseTools/tools_def: GCC5/CLANG38 toolchain updates
Date: Fri, 8 Dec 2017 14:26:12 +0000	[thread overview]
Message-ID: <20171208142612.nzyrtfbmlboupupb@bivouac.eciton.net> (raw)
In-Reply-To: <20171207205250.16312-1-ard.biesheuvel@linaro.org>

For the series:
Tested-by: Leif Lindholm <leif.lindholm@linaro.org>
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>

On Thu, Dec 07, 2017 at 08:52:47PM +0000, Ard Biesheuvel wrote:
> Some toolchain updates for CLANG38 and GCC5:
> - introduce CLANG38+LTO for ARM and AARCH64
> - disable a warning on CLANG38
> - enable optimization for GCC5 DEBUG builds
> 
> Ard Biesheuvel (3):
>   BaseTools/tools_def: add CLANG38 LTO versions for AARCH64 and ARM
>   BaseTools/tools_def CLANG38: add -Wno-unused-const-variable
>   BaseTool/tools_def GCC5: enable optimization for ARM/AARCH64 DEBUG
>     builds
> 
>  BaseTools/Conf/tools_def.template | 106 ++++++++++++++++++--
>  1 file changed, 99 insertions(+), 7 deletions(-)
> 
> -- 
> 2.11.0
> 


  parent reply	other threads:[~2017-12-08 14:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 20:52 [PATCH v3 0/3] BaseTools/tools_def: GCC5/CLANG38 toolchain updates Ard Biesheuvel
2017-12-07 20:52 ` [PATCH v3 1/3] BaseTools/tools_def: add CLANG38 LTO versions for AARCH64 and ARM Ard Biesheuvel
2017-12-07 20:52 ` [PATCH v3 2/3] BaseTools/tools_def CLANG38: add -Wno-unused-const-variable Ard Biesheuvel
2017-12-07 20:52 ` [PATCH v3 3/3] BaseTool/tools_def GCC5: enable optimization for ARM/AARCH64 DEBUG builds Ard Biesheuvel
2017-12-08 14:26 ` Leif Lindholm [this message]
2017-12-08 14:52   ` [PATCH v3 0/3] BaseTools/tools_def: GCC5/CLANG38 toolchain updates Gao, Liming
2017-12-08 15:10     ` Ard Biesheuvel

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=20171208142612.nzyrtfbmlboupupb@bivouac.eciton.net \
    --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