From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>,
Leif Lindholm <leif.lindholm@linaro.org>
Cc: "Tan, Sau Kae" <sau.kae.tan@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: question about armclang support
Date: Wed, 11 Jul 2018 09:50:34 +0200 [thread overview]
Message-ID: <CAKv+Gu8ZXdz_78w7daxwZY4UY=WYTmLY4hiEYyPtJrbieQzPCg@mail.gmail.com> (raw)
In-Reply-To: <9d0571e6-6b0d-15d7-ddde-adeec6ac4228@redhat.com>
(+ Leif)
On 10 July 2018 at 15:14, Laszlo Ersek <lersek@redhat.com> wrote:
> Hello Sau Kae,
>
> On 07/10/18 11:14, Tan, Sau Kae wrote:
>> Hi All,
>>
>> May I know is armclang already supported in EDK2?
>> Or only armcc is supported currently?
>> Thanks.
>
> Looking at "BaseTools/Conf/tools_def.template", the following toolchains appear supported for both ARM and AARCH64:
> - CLANG35
> - CLANG38
>
> They are documented (in the same file) as:
>
> # CLANG35 -Linux,Windows- Requires:
> # Clang v3.5 or later, and GNU binutils targeting aarch64-linux-gnu or arm-linux-gnueabi
> # Optional:
> # Required to build platforms or ACPI tables:
> # Intel(r) ACPI Compiler from
> # https://acpica.org/downloads
> # CLANG38 -Linux- Requires:
> # Clang v3.8, LLVMgold plugin and GNU binutils 2.26 targeting x86_64-linux-gnu, aarch64-linux-gnu or arm-linux-gnueabi
> # Clang v3.9 or later, LLVMgold plugin and GNU binutils 2.28 targeting x86_64-linux-gnu, aarch64-linux-gnu or arm-linux-gnueabi
> # Optional:
> # Required to build platforms or ACPI tables:
> # Intel(r) ACPI Compiler from
> # https://acpica.org/downloads
>
I suppose ARMCLANG is the commercial ARM compiler based on LLVM/CLANG?
In that case, could you please share your experiences with these
toolchain profiles? CLANG3x support was added primarily to ensure the
code base is supported by ARMCLANG but I don't know whether anyone has
actually tried building it like that.
prev parent reply other threads:[~2018-07-11 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 9:14 question about armclang support Tan, Sau Kae
2018-07-10 13:14 ` Laszlo Ersek
2018-07-11 7:50 ` Ard Biesheuvel [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='CAKv+Gu8ZXdz_78w7daxwZY4UY=WYTmLY4hiEYyPtJrbieQzPCg@mail.gmail.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