From: "Steven Shi" <steven.shi@intel.com>
To: "Lin, Derek (HPS SW)" <derek.lin2@hpe.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] BaseTools --hash malfunction after migrate from stable201905 to stable201908
Date: Sun, 29 Sep 2019 02:31:49 +0000 [thread overview]
Message-ID: <06C8AB66E78EE34A949939824ABE2B31401A4080@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <13576.1569571035464933693@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
Hi Derek,
Thank you for the data. I will continue to enhance the –hash performance, and will let you know after I figure out new solution.
Thanks
Steven Shi
Intel\SSG\SFE\FIE Firmware Infrastructure
From: Lin, Derek (HPS SW) [mailto:derek.lin2@hpe.com]
Sent: Friday, September 27, 2019 3:57 PM
To: Shi, Steven <steven.shi@intel.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] BaseTools --hash malfunction after migrate from stable201905 to stable201908
Hi Steven,
Thanks for the fix!
I've tried your patch with a minor fix as attached.
1 2 3 4
Build Duration: 00:05:51 00:03:47 00:05:15 00:04:31
AutoGen Duration: 00:03:32 00:03:08 00:03:14 00:03:16
Make Duration: 00:01:50 00:00:16 00:01:29 00:00:50
GenFds Duration: 00:00:30 00:00:22 00:00:31 00:00:23
1: clean build with patch and --hash
2: incremental build
3. clean build without patch and without --hash
4. incremental build
BTW, this data cannot compare with previous data I provided because they are built in different environment.
In general, the result is as you said that it fix --hash functionality, but not as quick as before.
Also the cost of --hash in clean build is increased.
[-- Attachment #2: Type: text/html, Size: 5782 bytes --]
next prev parent reply other threads:[~2019-09-29 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 6:54 BaseTools --hash malfunction after migrate from stable201905 to stable201908 Lin, Derek (HPS SW)
2019-09-23 7:51 ` Steven Shi
2019-09-24 8:12 ` Steven Shi
2019-09-27 7:57 ` [edk2-devel] " Lin, Derek (HPS SW)
2019-09-29 2:31 ` Steven Shi [this message]
2019-10-21 5:27 ` Steven Shi
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=06C8AB66E78EE34A949939824ABE2B31401A4080@shsmsx102.ccr.corp.intel.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