public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Jordan Justen <jordan.l.justen@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 1/2] EmulatorPkg/Unix/Host: Add GCC5 CC/DLINK commands (for GCC >= 5)
Date: Tue, 6 Jun 2017 19:18:05 +0200	[thread overview]
Message-ID: <d9d6bd0f-5152-ef30-6b81-b26dc2f5cf2d@redhat.com> (raw)
In-Reply-To: <CAKv+Gu801DT1yB6WtQLMFvfGA0M6gYgu8BVA-9D2Mx44mOAG6A@mail.gmail.com>

On 06/06/17 13:10, Ard Biesheuvel wrote:
> On 5 June 2017 at 18:33, Jordan Justen <jordan.l.justen@intel.com> wrote:
>> On 2017-06-02 14:48:14, Laszlo Ersek wrote:
>>> On 06/02/17 11:03, Ard Biesheuvel wrote:
>>>> On 1 June 2017 at 23:56, Jordan Justen <jordan.l.justen@intel.com> wrote:
>>>>
>>>> A commit log would be nice
>>>
>>> I agree. FWIW:
>>
>> How about this?
>>
>> EmulatorPkg/Unix/Host: Add GCC5 CC/DLINK commands (for GCC >= 5)
>>
>> These flags are based on the flags from the GCC5 toolchain in
>> tools_def.template. Since the GCC5 toolchain uses link-time
>> optimizations (LTO), we must compile and link the 'Host' files with
>> LTO enabled so we can link to other modules.
>>
> 
> Perfect.
> 

+1


      reply	other threads:[~2017-06-06 17:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 23:56 [PATCH 1/2] EmulatorPkg/Unix/Host: Add GCC5 CC/DLINK commands (for GCC >= 5) Jordan Justen
2017-06-01 23:56 ` [PATCH 2/2] EmulatorPkg/build.sh: Merge GCC toolchain detection from OVMF Jordan Justen
2017-06-02 21:50   ` Laszlo Ersek
2017-06-02  9:03 ` [PATCH 1/2] EmulatorPkg/Unix/Host: Add GCC5 CC/DLINK commands (for GCC >= 5) Ard Biesheuvel
2017-06-02 21:48   ` Laszlo Ersek
2017-06-05 18:33     ` Jordan Justen
2017-06-06 11:10       ` Ard Biesheuvel
2017-06-06 17:18         ` Laszlo Ersek [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=d9d6bd0f-5152-ef30-6b81-b26dc2f5cf2d@redhat.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