Chris Kay 2f1c5e7eb1 build: use GCC to link by default ... When configuring GNU GCC as the C compiler, we usually use the GNU BFD linker directly to link by default. However, this complicates things because we also need to support LTO, which can only be done when linking is done via the C compiler, and we cannot change the linker later on if some other part of the build system wants to enable LTO. This change migrates the default choice of linker to GCC if the C compiler is GCC, in order to enable this use-case. This should have no impact on anything outside of the build system, as by default GCC merely acts as a wrapper around BFD. Change-Id: I40771be2b0571def67bbfde9e877e7629ec8cdaa Signed-off-by: Chris Kay <chris.kay@arm.com>		2024-04-02 09:52:17 +00:00
..
amlogic	build: use new toolchain variables for tools	2024-02-06 11:14:52 +00:00
cert_create	build: use new toolchain variables for tools	2024-02-06 11:14:52 +00:00
conventional-changelog-tf-a	docs(changelog): changelog for v2.10 release	2023-11-22 11:52:02 +00:00
encrypt_fw	build: use new toolchain variables for tools	2024-02-06 11:14:52 +00:00
fiptool	build: use new toolchain variables for tools	2024-02-06 11:14:52 +00:00
marvell/doimage	build: use new toolchain variables for tools	2024-02-06 11:14:52 +00:00
memory	feat(memmap): add RELA section display	2024-01-18 14:02:18 +01:00
nxp	build: use new toolchain variables for tools	2024-02-06 11:14:52 +00:00
renesas	build: use GCC to link by default	2024-04-02 09:52:17 +00:00
sptool	build: use new toolchain variables for tools	2024-02-06 11:14:52 +00:00
stm32image	build: use new toolchain variables for tools	2024-02-06 11:14:52 +00:00