On 7 August 2015 at 18:54, Jordan Justen wrote:
> On 2015-08-07 07:59:24, Ard Biesheuvel wrote:
>> On 7 August 2015 at 16:51, Jordan Justen wrote:
>> > I think the subject should say 'Add CLANG toolchain with AARCH64
>> > support' to highlight that a new toolchain name is being defined.
>> >
>>
>
On 2015-08-07 07:59:24, Ard Biesheuvel wrote:
> On 7 August 2015 at 16:51, Jordan Justen wrote:
> > I think the subject should say 'Add CLANG toolchain with AARCH64
> > support' to highlight that a new toolchain name is being defined.
> >
>
> OK. I can fix that up before applying.
>
> > Should w
On 7 August 2015 at 16:59, Ard Biesheuvel wrote:
> On 7 August 2015 at 16:51, Jordan Justen wrote:
>> I think the subject should say 'Add CLANG toolchain with AARCH64
>> support' to highlight that a new toolchain name is being defined.
>>
>
> OK. I can fix that up before applying.
>
>> Should we
On 7 August 2015 at 16:51, Jordan Justen wrote:
> I think the subject should say 'Add CLANG toolchain with AARCH64
> support' to highlight that a new toolchain name is being defined.
>
OK. I can fix that up before applying.
> Should we consider adding the version to the toolchain name, like
> CL
I think the subject should say 'Add CLANG toolchain with AARCH64
support' to highlight that a new toolchain name is being defined.
Should we consider adding the version to the toolchain name, like
CLANG37? Then we can change parameters between major releases. At
least for GCC it has proved useful.
This adds support for building the AARCH64 platforms using the
Clang compiler and assembler combined with the GNU (cross-)linker.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
Reviewed-by: Leif Lindholm
Tested-by: Leif Lindholm
---
BaseTools/Conf/tools_d
6 matches
Mail list logo
