From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Holler Date: Sat, 19 Feb 2011 14:19:07 +0100 Subject: [U-Boot] [RFC][PATCH] ARMV7: Patch to fix hard float build issues In-Reply-To: References: <1298042212-12260-1-git-send-email-raghuveer.murthy@ti.com> <4D5EA603.8010402@free.fr> Message-ID: <4D5FC34B.5050309@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 Hello, Am 19.02.2011 12:19, schrieb M?ns Rullg?rd: >> In no case, however, should -msoft-float be *removed*: that would make >> float support in U-Boot implicit and dependent on the toolchain in use, >> and I think U-Boot float support should always be explicit and not >> depend on the toolchain. > > There is no reason for supporting hardware floating-point in u-boot. If > floating-point is used at all, and I can't think of a place where it is, > it is not relevant to performance. The added complexity of supporting a > hardware FPU is not worth it, in my opinion. I still don't understand this discussion. Floats aren't used in u-boot, so why should it make a difference if -msoft-float will be removed? I know there was one bug which linked in something wrong from glibc, but if that flag isn't needed than it shouldn't make a difference at all if -msoft-float or -mhard-float is used. So whats the reasoning to use -msoft-float as it is currently done? To confuse people? ;) Regards, Alexander