-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Rebecca Cran
Sent: Monday, April 3, 2023 7:28 AM
To: Gerd Hoffmann <[email protected]>
Cc: Leif Lindholm <[email protected]>; Ard Biesheuvel
<[email protected]>; [email protected]; Pedro Falcato
<[email protected]>; Gao, Liming <[email protected]>; Oliver Smith-Denny
<[email protected]>; Jiang, Guomin
<[email protected]>; Lu, Xiaoyu1 <[email protected]>; Wang, Jian J
<[email protected]>; Yao, Jiewen
<[email protected]>; Ard Biesheuvel <[email protected]>; Justen, Jordan L
<[email protected]>; Feng,
Bob C <[email protected]>; Andrew Fish <[email protected]>; Kinney, Michael D
<[email protected]>
Subject: Re: 回复: [edk2-devel] [PATCH v2 00/13]
BaseTools,CryptoPkg,MdePkg,OvmfPkg: Delete CLANG35,CLANG38,GCC48,GCC49,
rename GCC5 to GCC, update CLANGDWARF, delete VS 2008-2013, EBC
On 4/3/23 8:08 AM, Gerd Hoffmann wrote:
So you want gcc-6 specifically or just an older version instead of
latest? I could try add a RHEL-8 container (which ships gcc-8).
I'd want the oldest version that we support, so we know when we add
incompatible code.
From Pedro's reply, it sounds like that'll be gcc 5 once we add
-std=c++11 to tools_def.txt.template.
Well, I've wondered whenever it makes sense to do _less_ stuff in
parallel, to get down the constant overhead (clone repos etc).
Especially with a limit on parallel jobs that could be faster
in the end ...
Maybe a combination? For example one task that I think could do with
being split up to run in parallel is the following:
stuart_ci_build -c .pytool/CISettings.py -p CryptoPkg -t
DEBUG,RELEASE,NO-TARGET,NOOPT -a IA32,X64 TOOL_CHAIN_TAG=VS2019
(from
https://dev.azure.com/tianocore/edk2-ci/_build/results?buildId=85605&view=logs&j=c0929384-5a08-5c0f-b36d-
6f51b6b81732&t=f12d60be-1b97-57a4-b1ea-5aae2f026d4f)
It shows two tasks taking 13 minutes each.
--
Rebecca Cran
