From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Mon, 14 May 2012 23:11:26 -0600 Subject: [U-Boot] [PATCH 9/9] tegra2: Remove USE_PRIVATE_LIBGCC and armv4t build flags In-Reply-To: <1336633347-8049-10-git-send-email-amartin@nvidia.com> References: <1336633347-8049-1-git-send-email-amartin@nvidia.com> <1336633347-8049-10-git-send-email-amartin@nvidia.com> Message-ID: <4FB1E57E.4090308@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 05/10/2012 01:02 AM, Allen Martin wrote: > These flags were necessary when building tegra2 as a single binary > that supported ARM7TDMI and Cortex A9. Now that the ARM7TDMI support > is split into a separate SPL, this is no longer necessary. > diff --git a/arch/arm/cpu/armv7/tegra2/config.mk b/arch/arm/cpu/armv7/tegra2/config.mk > -# Tegra has an ARMv4T CPU which runs board_init_f(), so we must build this > -# file with compatible flags > -ifdef CONFIG_TEGRA2 > -CFLAGS_arch/arm/lib/board.o += -march=armv4t > -endif That makes sense since the CFLAGS for the SPL build will be set up appropriately for the AVP. > -USE_PRIVATE_LIBGCC = yes However, we force this because the toolchains we typically use for U-Boot are targeted at the A9 CPUs, and hence the libgcc there contains ARMv7 instructions. Did I miss something in this series or earlier that uses a different toolchain for the SPL, which includes an ARMv4 build of libgcc?