From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Thu, 05 Jan 2012 12:40:45 -0700 Subject: [U-Boot] [PATCH 1/2] tegra2: Always build with USE_PRIVATE_LIBGCC=yes. In-Reply-To: <20120105191614.2732FB6F26@gemini.denx.de> References: <1321524246-5187-1-git-send-email-thierry.reding@avionic-design.de> <1321524246-5187-2-git-send-email-thierry.reding@avionic-design.de> <20120105155033.52FFC1FC941@gemini.denx.de> <4F05D596.6030900@nvidia.com> <20120105191614.2732FB6F26@gemini.denx.de> Message-ID: <4F05FCBD.2040207@nvidia.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 01/05/2012 12:16 PM, Wolfgang Denk wrote: > In message <4F05D596.6030900@nvidia.com> you wrote: ... >> The libraries included in the toolchain are built for the ARMv7 CPUs, > > SO this is not the right tool chain for the job. Ecactly what I said. > >> and hence fail to operate correctly when used by the portion of U-Boot >> which runs on the ARMv4 CPU, presumably due to ISA differences. IIRC, >> there are overrides in the U-Boot build process such that some/all of >> U-Boot is built so it'll run on ARMv4 OK, which is why using libgcc >> built by U-Boot solves this. > > No, this is NOT a solution, it is a workaround for an inappropriate > toolchain. If you want to build code for an armv4t system, you must > use a tool chain that supports it. But we don't want to generate code for ARMv4 in general, but rather ARMv7 as the toolchain does. Only a tiny part of the code needs to be built for ARMv4, and in general we want to benefit from using ARMv7. -- nvpublic