From: B.R. Oake <broake@openmailbox.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Cannot compile arm u-boot with hardfloat toolchain
Date: Mon, 05 Jan 2015 15:30:49 +0000 [thread overview]
Message-ID: <54AAAE29.7040801@openmailbox.org> (raw)
In-Reply-To: <20150105133729.GF10826@bill-the-cat>
On 05/01/15 13:37, Tom Rini wrote:
> On Mon, Jan 05, 2015 at 12:24:13PM +0000, B.R. Oake wrote:
>> I still wonder though whether a nicer way would be for the configs to be
>> refactored so that -msoft-float was not set on platforms where it wasn't
>> appropriate.
>
> We've gone over this before (so there's discussions in the archive) but
> in sum, no, we don't want to get into doing floating point.
Hi Tom,
OK, I'll look for those discussions for more background. Just in case
there's any misunderstanding, though, I wasn't advocating using floating
point, I just meant that U-Boot code might want to perform operations
such as long long integer division, which will invoke a libgcc function
such as __udivdi3(), and for the linking to succeed we need to ensure
that U-Boot and libgcc are using the same ABI. On a fully hard-float
system, removing the -msoft-float compilation option seems a good way of
achieving that.
Thanks,
B.R.
next prev parent reply other threads:[~2015-01-05 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 22:23 [U-Boot] Cannot compile arm u-boot with hardfloat toolchain Michal Suchanek
2015-01-05 1:28 ` Tom Rini
2015-01-05 9:46 ` Michal Suchanek
2015-01-05 10:46 ` B.R. Oake
2015-01-05 10:51 ` Hans de Goede
2015-01-05 12:08 ` Michael Trimarchi
2015-01-05 12:24 ` B.R. Oake
2015-01-05 13:37 ` Tom Rini
2015-01-05 15:30 ` B.R. Oake [this message]
2015-01-05 14:58 ` Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54AAAE29.7040801@openmailbox.org \
--to=broake@openmailbox.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.