From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [Patch 4/4] BaseTools Makefile: Enable Ofast option for GCC tool chain
Date: Fri, 30 Sep 2016 11:49:28 +0200 [thread overview]
Message-ID: <dcdc6786-5af4-9859-9e62-85fec50ab4e3@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14B47F136@shsmsx102.ccr.corp.intel.com>
On 09/30/16 08:56, Gao, Liming wrote:
> Ersek:
>
> I try O2 option. Compared to Ofast, there is a little different. I
> think it is acceptable. I will use O2 option. And, this warning message
> also exists without O2 enable. It is not introduced by this patch.
>
>
>
> Tool Compression time
> Decompression time
>
> LzmaCompress (GCC O0) 3.476s 0.204s
>
> LzmaCompress (GCC Ofast) 1.655s 0.107s
>
> LzmaCompress (GCC O2) 1.687s 0.105s
>
Thank you very much!
Laszlo
next prev parent reply other threads:[~2016-09-30 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 14:12 [Patch 0/4] BaseTools: Enable optimization to generate fast code in C tools Liming Gao
2016-09-29 14:12 ` [Patch 1/4] BaseTools EfiLdrImage: Remove unnecessary exit (0) Liming Gao
2016-09-29 14:12 ` [Patch 2/4] BaseTools Makefile: Enable O2 option to replace Od for VS tool chain Liming Gao
2016-09-29 14:12 ` [Patch 3/4] BaseTools GenVtf: Initialize the return point as NULL Liming Gao
2016-09-29 14:12 ` [Patch 4/4] BaseTools Makefile: Enable Ofast option for GCC tool chain Liming Gao
2016-09-29 18:29 ` Laszlo Ersek
2016-09-30 0:24 ` Gao, Liming
2016-09-30 6:56 ` Gao, Liming
2016-09-30 9:49 ` Laszlo Ersek [this message]
2016-09-30 17:46 ` [Patch 0/4] BaseTools: Enable optimization to generate fast code in C tools Jordan Justen
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=dcdc6786-5af4-9859-9e62-85fec50ab4e3@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