diff options
| author | Oliver Smith-Denny <osde@microsoft.com> | 2025-02-28 16:17:18 -0800 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2025-03-12 06:04:35 +0000 |
| commit | 81031a51a0148a5ff7904f02cc405c8f3b910c55 (patch) | |
| tree | 4f4cde13955014864cf8b00824404d07614d97a8 /FatPkg | |
| parent | 03e66e0a03e8b81daf959cb4a886037cce506e2b (diff) | |
| download | edk2-master.zip edk2-master.tar.gz edk2-master.tar.bz2 | |
VS2019/VS2022 ARM/AARCH64 is not a widely used toolchain, for one
thing edk2 can't be built with it, it will break. Downstream
platforms rarely use it and if they do, they must have heavy edits
in order to support building edk2. In particular, edk2 does not
have support for the assembly files that this toolchain uses fully.
As a result, the corresponding StackCheckLib does not have the assembly
file needed to satisfy the definitions the compiler expects.
Unfortunately, the VS ARM/AARCH64 compiler has a different ABI than
the IA32/X64 VS toolchain for stack cookies, so this also needs more
investigation.
For now, disable stack cookie checking in VS ARM/AARCH64 as this does
not affect many platforms. However, it does allow for the use case
reported in the bug mentioning this, which is building a shell and
attempting to boot to it.
When VS ARM/AARCH64 support is revisited in edk2 (or if there is a
clean way to add stack cookie support without the full support), this
will be revisted.
Signed-off-by: Oliver Smith-Denny <osde@microsoft.com>
Diffstat (limited to 'FatPkg')
0 files changed, 0 insertions, 0 deletions