EDK II (mirror) https://git.radix-linux.su/Tianocore/edk2.git/atom?h=dependabot%2Fgithub_actions%2Factions%2Fgithub-script-9 2026-04-28T01:30:25+00:00 2026-04-28T01:30:25+00:00 Yang Gang yanggang@byosoft.com.cn 2026-04-09T08:39:52+00:00 urn:sha1:3449c60bab697665c0f8fc2cbc5d17ef2476ee6c Signed-off-by: Yang Gang <yanggang@byosoft.com.cn> 2026-04-15T01:57:51+00:00 Oliver Smith-Denny osde@microsoft.com 2026-03-23T16:11:02+00:00 urn:sha1:0d44f421a58fcbb48d268a31982e68a0712dc3b2 Currently, CLANGPDB X64 has 4KB section alignment and unwind tables. CLANGDWARF has neither. 4KB section alignment is up for review in a separate PR, so this commit adds unwind tables to DEBUG/NOOPT, matching both CLANGPDB and other toolchains. Signed-off-by: Oliver Smith-Denny <osde@microsoft.com> 2026-04-15T01:57:51+00:00 Oliver Smith-Denny osde@microsoft.com 2026-03-23T14:42:26+00:00 urn:sha1:192b5a92b36b77402db625350d8b288c9e74a3be Currently, the CLANGDWARF definitions for AARCH64 and RISCV64 (which was copied from the AARCH64 definitions originally) don't follow the same pattern as CLANGDWARF IA32/X64 and the rest of tools_def.template. This makes it harder to read and easier to make an error (e.g. other toolchain define cc/dlink flags in debug, release, noopt order, they do it in debug, noopt, release order, so it would be easy to swap flags intended for release and noopt). This is a whitespace and comment only change, no flags are changed. Signed-off-by: Oliver Smith-Denny <osde@microsoft.com> 2026-04-11T00:40:10+00:00 Michael D Kinney michael.d.kinney@intel.com 2026-04-09T23:32:40+00:00 urn:sha1:d4a6e02659bf9bd448e276e238f258fb8aaea29f Fix CLANGDWARF OBJCOPY errors for AARCH64 and RISCV64 by setting OBJCOPY_FLAGS to an empty string so OBJCOPY actions do not generate an error. This matches the IA32 and X64 settings for CLANGDWARF OBJCOPY_FLAGS. Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com> 2026-04-10T05:14:40+00:00 Yeoreum Yun yeoreum.yun@arm.com 2026-03-30T11:44:28+00:00 urn:sha1:ec1f28670a52c3d7ec8cbe8a61e1015b8ab8cba7 StandaloneMm is loaded failure when it built with clang-22. This is because mMmMemoryMap is intialised incorrectly by compiler: MmMain - 0xFF025040 [StandaloneMmMain:849] mMmMemoryMap: 0xFF21D238 [StandaloneMmMain:850] mMmMemoryMap->ForwardLink: 0xFF201000 [StandaloneMmMain:851] mMmMemoryMap->BackLink: 0xFF201000 The 0xFF20100 is loaded image address. However list_head -- mMemoryMap doesn't initialised properly by ld-lld. Here, ld with gcc initialised mMmMemoryMap list head properly: // 0x12490: &mMmMemoryMap # hexdump -Cv -s 0x12490 -n 64 StandaloneMmCore.efi 00012490 90 24 01 00 00 00 00 00 90 24 01 00 00 00 00 00 |.$.......$......| ... However, ld-lld with clang doesn't: // 0x1c238: &mMmMemoryMap # hexdump -Cv -s 0x1c238 -n 64 StandaloneMmCore.efi 0001c238 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| To address this, add --apply-dynamic-relocs linker option. After this patch, StandaloneMm is loaded preoperly and mMmMemoryMap is intialised correctly: ld-lld with clang with --aply-dynamic-reclos option: // 0x1d238: &mMmMemoryMap # hexdump -Cv -s 0x1d238 -n 64 StandaloneMmCore.efi 0001d238 38 d2 01 00 00 00 00 00 38 d2 01 00 00 00 00 00 |8.......8.......| Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com> 2026-04-02T19:56:18+00:00 Aaron Pop aaronpop@microsoft.com 2025-08-29T22:06:27+00:00 urn:sha1:87e486f622c5eaa0bee04f090b5c543466d6178b Reordering x64 toolchain defines (GCCS) to use a DLINK_XIPFLAGS to set common-page-size to 0x40. Otherwise use default align (0x1000 for x64). Reorder CLANGDWARF toolchain defines to use DLINK_XIPFLAGS to set common-page-size to 0x40 (matching existing behavior) and otherwise use default linker value (0x1000 for x64). Required modifying build_rule.template to support CLANGDWARF build family for SEC, PEI_CORE, PEIM type files. Signed-off-by: Aaron Pop <aaronpop@microsoft.com> 2026-03-06T19:47:31+00:00 Michael D Kinney michael.d.kinney@intel.com 2026-01-31T22:34:58+00:00 urn:sha1:e22f4a61c9e68fdf18e5dc202c9b1495f5cdca05 Add --source-code-format option that can be NASM or not specified. This can be used for file format specific actions when --source-code is used. A NASM specific action is added to convert #line to %line to preserve reference the originating NASM source file for source level debug in NASM format. Without this change, the source level debug of NASM files loads the generated intermediate file in the build output directory. Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com> 2026-02-26T23:33:31+00:00 Mike Beaton mjsbeaton@gmail.com 2026-02-26T15:52:02+00:00 urn:sha1:67bc9959ae0a23ac1ea5722d8391c294fb174cc7 Since ae83c6b7fd83a5906e016a32027c1bcd792a624e -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-unused-variable warning suppression is no longer needed in any builds, and the warnings can be re-enabled to catch real errors. Signed-off-by: Mike Beaton <mjsbeaton@gmail.com> 2026-02-26T15:30:52+00:00 Mike Beaton mjsbeaton@gmail.com 2026-01-24T15:57:58+00:00 urn:sha1:bdadb269e379cb32281fb7434ebb8f8d1b9e0b60 Update version to 3.06 with comment on changes. Signed-off-by: Mike Beaton <mjsbeaton@gmail.com> 2026-02-26T15:30:52+00:00 Mike Beaton mjsbeaton@gmail.com 2026-01-24T15:56:41+00:00 urn:sha1:575683811d9de952c9eeb8a91b112e78c8af4448 Signed-off-by: Mike Beaton <mjsbeaton@gmail.com>