On 23 July 2016 at 03:34, Jordan Justen wrote:
> On 2016-07-22 14:46:54, Ard Biesheuvel wrote:
>> On 22 July 2016 at 23:19, Jordan Justen wrote:
>> > I think the subject should include be something like "add GCC5
>> > toolchain for
On 2016-07-22 14:46:54, Ard Biesheuvel wrote:
> On 22 July 2016 at 23:19, Jordan Justen wrote:
> > I think the subject should include be something like "add GCC5
> > toolchain for X64/AARCH64 with LTO support".
> >
> > On 2016-07-18 05:09:15, Ard Biesheuvel wrote:
> >>
On 22 July 2016 at 23:19, Jordan Justen wrote:
> I think the subject should include be something like "add GCC5
> toolchain for X64/AARCH64 with LTO support".
>
> On 2016-07-18 05:09:15, Ard Biesheuvel wrote:
>> This adds support for GCC 5.x in LTO mode for IA32, X64,
I think the subject should include be something like "add GCC5
toolchain for X64/AARCH64 with LTO support".
On 2016-07-18 05:09:15, Ard Biesheuvel wrote:
> This adds support for GCC 5.x in LTO mode for IA32, X64, ARM and
> AARCH64. Due to the fact that the GCC project switched to a new
>
On 22 July 2016 at 10:38, Gao, Liming wrote:
> Ard:
> I have some comments on GCC5 DLINK PATH definition. *_GCC5_*_DLINK_PATH
> = $(EDK_TOOLS_PATH)/Scripts/lto-ld-wrapper.py
> 1) It directly points to python script. In OS, python script need be trigged
> by
Ard:
I have some comments on GCC5 DLINK PATH definition. *_GCC5_*_DLINK_PATH
= $(EDK_TOOLS_PATH)/Scripts/lto-ld-wrapper.py
1) It directly points to python script. In OS, python script need be trigged by
python execute.
2) Most windows users directly use the binary base tools.
This adds support for GCC 5.x in LTO mode for IA32, X64, ARM and
AARCH64. Due to the fact that the GCC project switched to a new
numbering scheme where the first digit is now incremented for every
major release, the new toolchain is simply called 'GCC5', and is
intended to support all GCC v5.x
7 matches
Mail list logo