From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfgang Denk Date: Thu, 05 Jan 2012 21:17:09 +0100 Subject: [U-Boot] [PATCH 1/2] tegra2: Always build with USE_PRIVATE_LIBGCC=yes. In-Reply-To: <4F05FCBD.2040207@nvidia.com> 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> Message-ID: <20120105201709.1195DB6F26@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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. But as soon as any of these files liks code from libgcc you have to decide. > 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. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de I'd rather be led to hell than managed to heaven.