From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Holler Date: Sat, 19 Feb 2011 15:39:08 +0100 Subject: [U-Boot] [RFC][PATCH] ARMV7: Patch to fix hard float build issues In-Reply-To: <4D5FD35D.3090609@free.fr> References: <1298042212-12260-1-git-send-email-raghuveer.murthy@ti.com> <4D5EA603.8010402@free.fr> <4D5FC34B.5050309@ahsoftware.de> <4D5FCACA.1060606@free.fr> <4D5FCE64.8030901@ahsoftware.de> <4D5FD35D.3090609@free.fr> Message-ID: <4D5FD60C.6080701@ahsoftware.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 19.02.2011 15:27, schrieb Albert ARIBAUD: > Le 19/02/2011 15:06, Alexander Holler a ?crit : >> Am 19.02.2011 14:51, schrieb Albert ARIBAUD: >>> Le 19/02/2011 14:25, M?ns Rullg?rd a ?crit : >>> >>>>> So whats the reasoning to use -msoft-float as it is currently done? To >>>>> confuse people? ;) >> I don't see any reason to explicitly set an option for something which >> isn't used, but I know of many reasons to avoid such. ;) > > At least there is one reason for having -msoft-float even though no > floating point should be used in U-Boot : it helps catching cases where > some code in U-Boot tries to use hard float. :) > > Think of it as choosing the least dangerous of Charybdis and Scylla, > while trying our best not to get near any of the two. Hmm, I could argue exactly the oposite. When using -msoft-float you won't find (unwanted) usages of float on any platform. To follow your argument, hard-floats should be enabled (if possible), so the usage of floats would lead to an error (at least on platforms without support for that). ;) Regards, Alexander