public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Shi, Steven" <steven.shi@intel.com>
To: Bruce Cran <bruce@cran.org.uk>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>
Subject: Re: Build traceback with new CLANG35 toolset
Date: Wed, 3 Aug 2016 00:13:58 +0000	[thread overview]
Message-ID: <06C8AB66E78EE34A949939824ABE2B3103383DE7@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <86365dc5-f454-cbaa-b828-5030518be148@cran.org.uk>

Cran,
We will send CLANG38 patch to support X86, and the new CLANG38 patch will base on current GCC5 implementation. FYI.


Steven Shi
Intel\SSG\STO\UEFI Firmware

Tel: +86 021-61166522
iNet: 821-6522


> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Bruce Cran
> Sent: Wednesday, August 03, 2016 2:56 AM
> To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: edk2-devel-01 <edk2-devel@lists.01.org>
> Subject: Re: [edk2] Build traceback with new CLANG35 toolset
> 
> On 8/2/2016 12:53 PM, Ard Biesheuvel wrote:
> 
> > CLANG35 is not new, and currently only supports ARM and AARCH64
> 
> Oops - thanks. I was thinking of CLANG38 that hasn't been committed yet.
> 
> --
> Bruce
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2016-08-03  0:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 18:24 Build traceback with new CLANG35 toolset Bruce Cran
2016-08-02 18:53 ` Ard Biesheuvel
2016-08-02 18:55   ` Bruce Cran
2016-08-03  0:13     ` Shi, Steven [this message]

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=06C8AB66E78EE34A949939824ABE2B3103383DE7@shsmsx102.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