qiurui
/
glibc
mirror of git://sourceware.org/git/glibc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
glibc/sysdeps/unix/sysv/linux/aarch64/Makefile

179 lines
6.1 KiB
Makefile
Raw Normal View History

aarch64: Fix _dl_tlsdesc_dynamic unwind for pac-ret (BZ 32612) When libgcc is built with pac-ret, it requires to autenticate the unwinding frame based on CFI information. The _dl_tlsdesc_dynamic uses a custom calling convention, where it is responsible to save and restore all registers it might use (even volatile). The pac-ret support added by 1be3d6eb823d8b952fa54b7bbc90cbecb8981380 was added only on the slow-path, but the fast path also adds DWARF Register Rule Instruction (cfi_adjust_cfa_offset) since it requires to save/restore some auxiliary register. It seems that this is not fully supported neither by libgcc nor AArch64 ABI [1]. Instead, move paciasp/autiasp to function prologue/epilogue to be used on both fast and slow paths. I also corrected the _dl_tlsdesc_dynamic comment description, it was copied from i386 implementation without any adjustment. Checked on aarch64-linux-gnu with a toolchain built with --enable-standard-branch-protection on a system with pac-ret support. [1] https://github.com/ARM-software/abi-aa/blob/main/aadwarf64/aadwarf64.rst#id1 Reviewed-by: Yury Khrustalev <yury.khrustalev@arm.com>
2025-03-28 17:27:45 +00:00
ifeq ($(subdir),elf)
tests += \
tst-tlsdesc-pac \
# tests
modules-names += \
tst-tlsdesc-pac-mod \
# modules-names
LDFLAGS-tst-tlsdesc-pac = -rdynamic
$(objpfx)tst-tlsdesc-pac.out: $(objpfx)tst-tlsdesc-pac-mod.so
endif
AArch64 Port
2012-11-09 17:53:51 +00:00
ifeq ($(subdir),misc)
sysdep_headers += sys/elf.h
AArch64: Add support for memory protection keys This patch adds support for memory protection keys on AArch64 systems with enabled Stage 1 permission overlays feature introduced in Armv8.9 / 9.4 (FEAT_S1POE) [1]. 1. Internal functions "pkey_read" and "pkey_write" to access data associated with memory protection keys. 2. Implementation of API functions "pkey_get" and "pkey_set" for the AArch64 target. 3. AArch64-specific PKEY flags for READ and EXECUTE (see below). 4. New target-specific test that checks behaviour of pkeys on AArch64 targets. 5. This patch also extends existing generic test for pkeys. 6. HWCAP constant for Permission Overlay Extension feature. To support more accurate mapping of underlying permissions to the PKEY flags, we introduce additional AArch64-specific flags. The full list of flags is: - PKEY_UNRESTRICTED: 0x0 (for completeness) - PKEY_DISABLE_ACCESS: 0x1 (existing flag) - PKEY_DISABLE_WRITE: 0x2 (existing flag) - PKEY_DISABLE_EXECUTE: 0x4 (new flag, AArch64 specific) - PKEY_DISABLE_READ: 0x8 (new flag, AArch64 specific) The problem here is that PKEY_DISABLE_ACCESS has unusual semantics as it overlaps with existing PKEY_DISABLE_WRITE and new PKEY_DISABLE_READ. For this reason mapping between permission bits RWX and "restrictions" bits awxr (a for disable access, etc) becomes complicated: - PKEY_DISABLE_ACCESS disables both R and W - PKEY_DISABLE_{WRITE,READ} disables W and R respectively - PKEY_DISABLE_EXECUTE disables X Combinations like the one below are accepted although they are redundant: - PKEY_DISABLE_ACCESS | PKEY_DISABLE_READ | PKEY_DISABLE_WRITE Reverse mapping tries to retain backward compatibility and ORs PKEY_DISABLE_ACCESS whenever both flags PKEY_DISABLE_READ and PKEY_DISABLE_WRITE would be present. This will break code that compares pkey_get output with == instead of using bitwise operations. The latter is more correct since PKEY_* constants are essentially bit flags. It should be noted that PKEY_DISABLE_ACCESS does not prevent execution. [1] https://developer.arm.com/documentation/ddi0487/ka/ section D8.4.1.4 Co-authored-by: Szabolcs Nagy <szabolcs.nagy@arm.com> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2024-11-20 11:16:36 +00:00
tests += \
tst-aarch64-pkey \
# tests
aarch64: Add tests for Guarded Control Stack These tests validate that GCS tunable works as expected depending on the GCS markings in the test binaries. Tests validate both static and dynamically linked binaries. These new tests are AArch64 specific. Moreover, they are included only if linker supports the "-z gcs=<value>" option. If built, these tests will run on systems with and without HWCAP_GCS. In the latter case the tests will be reported as UNSUPPORTED. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-21 13:33:20 +00:00
aarch64: make GCS configure checks aarch64-only We only need to enable GCS tests on AArch64 targets, however previously the configure checks for GCS support in compiler and linker were added for all targets which was not efficient. To enable tests for GCS we need 4 things to be true: - Compiler supports GCS branch protection. - Test compiler supports GCS branch protection. - Linker supports GCS marking of binaries. - The CRT objects provided by the toolchain have GCS marking. To check for the latter, we add new macro to aclocal.m4 that allows to grep output from readelf. We check all four and then put the result in one make variable to simplify checks in makefiles. Reviewed-by: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
2025-11-24 11:20:57 +00:00
ifeq (yes,$(have-test-gcs))
aarch64: Add tests for Guarded Control Stack These tests validate that GCS tunable works as expected depending on the GCS markings in the test binaries. Tests validate both static and dynamically linked binaries. These new tests are AArch64 specific. Moreover, they are included only if linker supports the "-z gcs=<value>" option. If built, these tests will run on systems with and without HWCAP_GCS. In the latter case the tests will be reported as UNSUPPORTED. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-21 13:33:20 +00:00
gcs-tests-dynamic = \
tst-gcs-disabled \
aarch64: Add GCS tests for dlopen Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-22 17:21:26 +00:00
tst-gcs-dlopen-disabled \
tst-gcs-dlopen-enforced \
tst-gcs-dlopen-optional-off \
tst-gcs-dlopen-optional-on \
tst-gcs-dlopen-override \
aarch64: Add tests for Guarded Control Stack These tests validate that GCS tunable works as expected depending on the GCS markings in the test binaries. Tests validate both static and dynamically linked binaries. These new tests are AArch64 specific. Moreover, they are included only if linker supports the "-z gcs=<value>" option. If built, these tests will run on systems with and without HWCAP_GCS. In the latter case the tests will be reported as UNSUPPORTED. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-21 13:33:20 +00:00
tst-gcs-enforced \
tst-gcs-enforced-abort \
aarch64: Add LD_DEBUG=security to log BTI and GCS warnings Introduce DL_DEBUG_SECURITY mask to enable messages related to loading modules that lack certain target-dependent hardening or security features. Use this mask for warnings related to AArch64 BTI and GCS. Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
2026-01-06 13:43:34 +00:00
tst-gcs-ld-debug-both \
tst-gcs-ld-debug-dlopen \
tst-gcs-ld-debug-exe \
tst-gcs-ld-debug-shared \
aarch64: Add GCS test with signal handler Test that when we return from a function that enabled GCS at runtime we get SIGSEGV. Also test that ucontext contains GCS block with the GCS pointer. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-23 10:36:36 +00:00
tst-gcs-noreturn \
aarch64: Add tests for Guarded Control Stack These tests validate that GCS tunable works as expected depending on the GCS markings in the test binaries. Tests validate both static and dynamically linked binaries. These new tests are AArch64 specific. Moreover, they are included only if linker supports the "-z gcs=<value>" option. If built, these tests will run on systems with and without HWCAP_GCS. In the latter case the tests will be reported as UNSUPPORTED. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-21 13:33:20 +00:00
tst-gcs-optional-off \
tst-gcs-optional-on \
tst-gcs-override \
aarch64: Add GCS tests for transitive dependencies Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-22 15:06:18 +00:00
tst-gcs-shared-disabled \
tst-gcs-shared-enforced-abort \
tst-gcs-shared-optional \
tst-gcs-shared-override \
aarch64: Add tests for Guarded Control Stack These tests validate that GCS tunable works as expected depending on the GCS markings in the test binaries. Tests validate both static and dynamically linked binaries. These new tests are AArch64 specific. Moreover, they are included only if linker supports the "-z gcs=<value>" option. If built, these tests will run on systems with and without HWCAP_GCS. In the latter case the tests will be reported as UNSUPPORTED. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-21 13:33:20 +00:00
# gcs-tests-dynamic
gcs-tests-static = \
tst-gcs-disabled-static \
tst-gcs-enforced-static \
tst-gcs-enforced-static-abort \
tst-gcs-optional-static-off \
tst-gcs-optional-static-on \
tst-gcs-override-static \
# gcs-tests-static
tests += \
$(gcs-tests-dynamic) \
$(gcs-tests-static) \
# tests
tests-static += \
$(gcs-tests-static) \
# tests-static
define run-gcs-abort-test
$(test-wrapper-env) $(run-program-env) \
$(tst-gcs-$*-abort-ENV) $(host-test-program-cmd)
endef
$(objpfx)tst-gcs-%-abort.out: $(..)sysdeps/unix/sysv/linux/aarch64/tst-gcs-abort.sh \
$(objpfx)tst-gcs-%-abort
$(SHELL) $< $(common-objpfx) $(test-name) '$(run-gcs-abort-test)'; \
$(evaluate-test)
aarch64: Fix gcs linker flags clang does not work by using whitespace for defining the -z option: $ make test t=misc/tst-gcs-disabled [...] clang: error: no such file or directory: 'gcs=always' Use the usual comma separate way. Reviewed-by: Florian Weimer <fweimer@redhat.com>
2025-10-17 19:13:11 +00:00
LDFLAGS-tst-gcs-disabled += -Wl,-z,gcs=always
LDFLAGS-tst-gcs-enforced += -Wl,-z,gcs=always
LDFLAGS-tst-gcs-enforced-abort += -Wl,-z,gcs=never
LDFLAGS-tst-gcs-optional-on += -Wl,-z,gcs=always
LDFLAGS-tst-gcs-optional-off += -Wl,-z,gcs=never
LDFLAGS-tst-gcs-override += -Wl,-z,gcs=never
LDFLAGS-tst-gcs-disabled-static += -Wl,-z,gcs=always
LDFLAGS-tst-gcs-enforced-static += -Wl,-z,gcs=always
aarch64: Add LD_DEBUG=security to log BTI and GCS warnings Introduce DL_DEBUG_SECURITY mask to enable messages related to loading modules that lack certain target-dependent hardening or security features. Use this mask for warnings related to AArch64 BTI and GCS. Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
2026-01-06 13:43:34 +00:00
LDFLAGS-tst-gcs-enforced-static-abort += -Wl,-z,gcs=never
aarch64: Fix gcs linker flags clang does not work by using whitespace for defining the -z option: $ make test t=misc/tst-gcs-disabled [...] clang: error: no such file or directory: 'gcs=always' Use the usual comma separate way. Reviewed-by: Florian Weimer <fweimer@redhat.com>
2025-10-17 19:13:11 +00:00
LDFLAGS-tst-gcs-optional-static-on += -Wl,-z,gcs=always
LDFLAGS-tst-gcs-optional-static-off += -Wl,-z,gcs=never
LDFLAGS-tst-gcs-override-static += -Wl,-z,gcs=never
aarch64: Add tests for Guarded Control Stack These tests validate that GCS tunable works as expected depending on the GCS markings in the test binaries. Tests validate both static and dynamically linked binaries. These new tests are AArch64 specific. Moreover, they are included only if linker supports the "-z gcs=<value>" option. If built, these tests will run on systems with and without HWCAP_GCS. In the latter case the tests will be reported as UNSUPPORTED. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-21 13:33:20 +00:00
tst-gcs-disabled-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=0
tst-gcs-enforced-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=1
tst-gcs-enforced-abort-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=1
tst-gcs-optional-on-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=2
tst-gcs-optional-off-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=2
tst-gcs-override-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=3
tst-gcs-disabled-static-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=0
tst-gcs-enforced-static-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=1
aarch64: Add LD_DEBUG=security to log BTI and GCS warnings Introduce DL_DEBUG_SECURITY mask to enable messages related to loading modules that lack certain target-dependent hardening or security features. Use this mask for warnings related to AArch64 BTI and GCS. Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
2026-01-06 13:43:34 +00:00
tst-gcs-enforced-static-abort-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=1
aarch64: Add tests for Guarded Control Stack These tests validate that GCS tunable works as expected depending on the GCS markings in the test binaries. Tests validate both static and dynamically linked binaries. These new tests are AArch64 specific. Moreover, they are included only if linker supports the "-z gcs=<value>" option. If built, these tests will run on systems with and without HWCAP_GCS. In the latter case the tests will be reported as UNSUPPORTED. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-21 13:33:20 +00:00
tst-gcs-optional-static-on-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=2
tst-gcs-optional-static-off-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=2
tst-gcs-override-static-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=3
aarch64: Add GCS tests for transitive dependencies Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-22 15:06:18 +00:00
# force one of the dependencies to be unmarked
aarch64: Fix gcs linker flags clang does not work by using whitespace for defining the -z option: $ make test t=misc/tst-gcs-disabled [...] clang: error: no such file or directory: 'gcs=always' Use the usual comma separate way. Reviewed-by: Florian Weimer <fweimer@redhat.com>
2025-10-17 19:13:11 +00:00
LDFLAGS-tst-gcs-mod2.so += -Wl,-z,gcs=never
aarch64: Add GCS tests for transitive dependencies Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-22 15:06:18 +00:00
aarch64: Fix gcs linker flags clang does not work by using whitespace for defining the -z option: $ make test t=misc/tst-gcs-disabled [...] clang: error: no such file or directory: 'gcs=always' Use the usual comma separate way. Reviewed-by: Florian Weimer <fweimer@redhat.com>
2025-10-17 19:13:11 +00:00
LDFLAGS-tst-gcs-shared-disabled = -Wl,-z,gcs=always
LDFLAGS-tst-gcs-shared-enforced-abort = -Wl,-z,gcs=always
LDFLAGS-tst-gcs-shared-optional = -Wl,-z,gcs=always
LDFLAGS-tst-gcs-shared-override = -Wl,-z,gcs=always
aarch64: Add GCS tests for transitive dependencies Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-22 15:06:18 +00:00
aarch64: Add LD_DEBUG=security to log BTI and GCS warnings Introduce DL_DEBUG_SECURITY mask to enable messages related to loading modules that lack certain target-dependent hardening or security features. Use this mask for warnings related to AArch64 BTI and GCS. Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
2026-01-06 13:43:34 +00:00
LDFLAGS-tst-gcs-ld-debug-shared = -Wl,-z,gcs=always
LDFLAGS-tst-gcs-ld-debug-dlopen = -Wl,-z,gcs=always
aarch64: Add GCS tests for transitive dependencies Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-22 15:06:18 +00:00
modules-names += \
tst-gcs-mod1 \
tst-gcs-mod2 \
tst-gcs-mod3 \
# modules-names
$(objpfx)tst-gcs-shared-disabled: $(objpfx)tst-gcs-mod1.so $(objpfx)tst-gcs-mod3.so
$(objpfx)tst-gcs-shared-enforced-abort: $(objpfx)tst-gcs-mod1.so $(objpfx)tst-gcs-mod3.so
$(objpfx)tst-gcs-shared-optional: $(objpfx)tst-gcs-mod1.so $(objpfx)tst-gcs-mod3.so
$(objpfx)tst-gcs-shared-override: $(objpfx)tst-gcs-mod1.so $(objpfx)tst-gcs-mod3.so
$(objpfx)tst-gcs-mod1.so: $(objpfx)tst-gcs-mod2.so
aarch64: Add LD_DEBUG=security to log BTI and GCS warnings Introduce DL_DEBUG_SECURITY mask to enable messages related to loading modules that lack certain target-dependent hardening or security features. Use this mask for warnings related to AArch64 BTI and GCS. Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
2026-01-06 13:43:34 +00:00
$(objpfx)tst-gcs-ld-debug-both: $(objpfx)tst-gcs-mod2.so
$(objpfx)tst-gcs-ld-debug-shared: $(objpfx)tst-gcs-mod1.so $(objpfx)tst-gcs-mod3.so
aarch64: Add GCS tests for transitive dependencies Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-22 15:06:18 +00:00
tst-gcs-shared-disabled-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=0
tst-gcs-shared-enforced-abort-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=1
tst-gcs-shared-optional-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=2
tst-gcs-shared-override-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=3
aarch64: Fix gcs linker flags clang does not work by using whitespace for defining the -z option: $ make test t=misc/tst-gcs-disabled [...] clang: error: no such file or directory: 'gcs=always' Use the usual comma separate way. Reviewed-by: Florian Weimer <fweimer@redhat.com>
2025-10-17 19:13:11 +00:00
LDFLAGS-tst-gcs-dlopen-disabled = -Wl,-z,gcs=always
LDFLAGS-tst-gcs-dlopen-enforced = -Wl,-z,gcs=always
LDFLAGS-tst-gcs-dlopen-optional-on = -Wl,-z,gcs=always
LDFLAGS-tst-gcs-dlopen-optional-off = -Wl,-z,gcs=never
LDFLAGS-tst-gcs-dlopen-override = -Wl,-z,gcs=always
aarch64: Add LD_DEBUG=security to log BTI and GCS warnings Introduce DL_DEBUG_SECURITY mask to enable messages related to loading modules that lack certain target-dependent hardening or security features. Use this mask for warnings related to AArch64 BTI and GCS. Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
2026-01-06 13:43:34 +00:00
LDFLAGS-tst-gcs-ld-debug-exe = -Wl,-z,gcs=never
LDFLAGS-tst-gcs-ld-debug-both = -Wl,-z,gcs=never
aarch64: Add GCS tests for dlopen Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-22 17:21:26 +00:00
tst-gcs-dlopen-disabled-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=0
tst-gcs-dlopen-enforced-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=1
tst-gcs-dlopen-optional-on-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=2
tst-gcs-dlopen-optional-off-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=2
tst-gcs-dlopen-override-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=3
$(objpfx)tst-gcs-dlopen-disabled.out: $(objpfx)tst-gcs-mod2.so
$(objpfx)tst-gcs-dlopen-enforced.out: $(objpfx)tst-gcs-mod2.so
$(objpfx)tst-gcs-dlopen-optional-on.out: $(objpfx)tst-gcs-mod2.so
$(objpfx)tst-gcs-dlopen-optional-off.out: $(objpfx)tst-gcs-mod2.so
$(objpfx)tst-gcs-dlopen-override.out: $(objpfx)tst-gcs-mod2.so
aarch64: Add LD_DEBUG=security to log BTI and GCS warnings Introduce DL_DEBUG_SECURITY mask to enable messages related to loading modules that lack certain target-dependent hardening or security features. Use this mask for warnings related to AArch64 BTI and GCS. Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
2026-01-06 13:43:34 +00:00
$(objpfx)tst-gcs-ld-debug-dlopen.out: $(objpfx)tst-gcs-mod2.so
aarch64: Add GCS tests for dlopen Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-22 17:21:26 +00:00
aarch64: Fix gcs linker flags clang does not work by using whitespace for defining the -z option: $ make test t=misc/tst-gcs-disabled [...] clang: error: no such file or directory: 'gcs=always' Use the usual comma separate way. Reviewed-by: Florian Weimer <fweimer@redhat.com>
2025-10-17 19:13:11 +00:00
LDFLAGS-tst-gcs-noreturn = -Wl,-z,gcs=always
aarch64: Add GCS test with signal handler Test that when we return from a function that enabled GCS at runtime we get SIGSEGV. Also test that ucontext contains GCS block with the GCS pointer. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-23 10:36:36 +00:00
tst-gcs-noreturn-ENV = GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=0
aarch64: Add LD_DEBUG=security to log BTI and GCS warnings Introduce DL_DEBUG_SECURITY mask to enable messages related to loading modules that lack certain target-dependent hardening or security features. Use this mask for warnings related to AArch64 BTI and GCS. Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>
2026-01-06 13:43:34 +00:00
$(objpfx)tst-gcs-ld-debug-%.out: $(..)elf/tst-dl-debug-protect.sh $(objpfx)tst-gcs-ld-debug-%
$(SHELL) $< $(objpfx) '$(test-wrapper-env)' '$(rtld-prefix)' \
'$(run-program-env) GLIBC_TUNABLES=glibc.cpu.aarch64_gcs=2' \
'security: not compatible with AArch64 GCS: $(objpfx)' \
$(objpfx)tst-gcs-ld-debug-$* > $@; $(evaluate-test)
aarch64: make GCS configure checks aarch64-only We only need to enable GCS tests on AArch64 targets, however previously the configure checks for GCS support in compiler and linker were added for all targets which was not efficient. To enable tests for GCS we need 4 things to be true: - Compiler supports GCS branch protection. - Test compiler supports GCS branch protection. - Linker supports GCS marking of binaries. - The CRT objects provided by the toolchain have GCS marking. To check for the latter, we add new macro to aclocal.m4 that allows to grep output from readelf. We check all four and then put the result in one make variable to simplify checks in makefiles. Reviewed-by: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
2025-11-24 11:20:57 +00:00
endif # ifeq ($(have-test-gcs),yes)
aarch64: Add tests for Guarded Control Stack These tests validate that GCS tunable works as expected depending on the GCS markings in the test binaries. Tests validate both static and dynamically linked binaries. These new tests are AArch64 specific. Moreover, they are included only if linker supports the "-z gcs=<value>" option. If built, these tests will run on systems with and without HWCAP_GCS. In the latter case the tests will be reported as UNSUPPORTED. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
2025-01-21 13:33:20 +00:00
endif # ifeq ($(subdir),misc)
AArch64 Port
2012-11-09 17:53:51 +00:00
ifeq ($(subdir),stdlib)
gen-as-const-headers += ucontext_i.sym
endif
[AArch64] Define BE loader name.
2014-01-01 17:29:23 +00:00
abi-variants := lp64
abi-variants += lp64_be
ifeq (,$(filter $(default-abi),$(abi-variants)))
Unknown ABI, must be one of $(abi-variants)
endif
abi-lp64-condition := !defined __AARCH64EB__
abi-lp64_be-condition := defined __AARCH64EB__