From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"lersek@redhat.com" <lersek@redhat.com>,
"Shi, Steven" <steven.shi@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>
Subject: Re: [PATCH v4 0/7] BaseTools: add support for GCC5 in LTO mode
Date: Fri, 29 Jul 2016 20:21:37 +0200 [thread overview]
Message-ID: <CAKv+Gu_mQLfGaNrBc8hMjZXys-SQE6k0fLAEu2vBm=_Ma8sbDg@mail.gmail.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A1155E2761@shsmsx102.ccr.corp.intel.com>
On 29 July 2016 at 17:18, Gao, Liming <liming.gao@intel.com> wrote:
> Ard:
>
> My gcc version 5.3.0 20151204 (Ubuntu 5.3.0-3ubuntu1~14.04). I will try
> GCC54.
>
Could you check if the issue also occurs with the 'old' GCC49, i.e.,
the version that uses LD as the linker?
>
>
> Besides, for new GCC5 tool chain, could you add one brief introduction in
> tools_def.txt like GCC49? And, highlight it enable LTO by default.
>
>
>
> # GCC49 -Linux,Windows- Requires:
>
> # GCC 4.9 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
>
OK
--
Ard.
next prev parent reply other threads:[~2016-07-29 18:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1469618017-6534-1-git-send-email-ard.biesheuvel@linaro.org>
2016-07-29 4:47 ` [PATCH v4 0/7] BaseTools: add support for GCC5 in LTO mode Gao, Liming
2016-07-29 6:09 ` Ard Biesheuvel
2016-07-29 6:40 ` Ard Biesheuvel
2016-07-29 15:18 ` Gao, Liming
2016-07-29 18:21 ` Ard Biesheuvel [this message]
2016-07-30 14:34 ` Ard Biesheuvel
2016-07-31 19:04 ` Ard Biesheuvel
2016-08-01 2:26 ` Gao, Liming
2016-08-01 6:03 ` Ard Biesheuvel
2016-07-29 20:33 ` Jordan Justen
2016-07-30 9:22 ` 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='CAKv+Gu_mQLfGaNrBc8hMjZXys-SQE6k0fLAEu2vBm=_Ma8sbDg@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