From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Thu, 05 Jan 2012 13:53:37 -0700 Subject: [U-Boot] [PATCH 1/2] tegra2: Always build with USE_PRIVATE_LIBGCC=yes. In-Reply-To: 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> <4F05FCBD.2040207@nvidia.com> <20120105201709.1195DB6F26@gemini.denx.de> Message-ID: <4F060DD1.9050907@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 01:42 PM, Simon Glass wrote: > Hi, > > On Thu, Jan 5, 2012 at 12:17 PM, Wolfgang Denk wrote: >> Dear Stephen Warren, >> >> In message <4F05FCBD.2040207@nvidia.com> you wrote: >>> >>>> 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 >> >> Then just turn on the ARMv4 specific options (-march=armv4t -mno-thumb >> -mthumb-interwork -mtune=arm920t ???) for the files that need it. That's exactly what we've already done, but that doesn't affect code that gets pulled in from libgcc, which is what USE_PRIVATE_LIBGCC affects IIUC. >> But as soon as any of these files liks code from libgcc you have to >> decide. > > Perhaps we could adjust Tegra's config.mk to use ARMv4T when not > building with the private libgcc? I believe the relevant U-Boot source files are already built for ARMv4T, it's just libgcc that's the issue. >>> 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. >> >> Then you should probably still link against a ARMv4 specific libgcc. >> >> If you were building U-Boot's libgcc code with optimization set for >> ARMv7 this would not fix anything. > > It might be possible to specify ARMv4T on the link flags and have it > pick up the v4T library, even if nearly everything else is ARMv7? I don't think we use any multilib toolchains, so I don't think that's possible. -- nvpublic