From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] powerpc/spe: tweak glibc/eglibc/uclibc combinations
Date: Thu, 11 Sep 2014 22:57:15 +0200 [thread overview]
Message-ID: <20140911225715.70f88987@free-electrons.com> (raw)
In-Reply-To: <1410436592-1990-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Thu, 11 Sep 2014 08:56:31 -0300, Gustavo Zacarias wrote:
> Since (e)glibc 2.19+ PowerPC SPE changed ABI conventions for sanity.
> In the good old days hard-float was used, it sounds good on paper until
> you account for the e500v1/v2 differences, with v1 being a fpu that does
> only single-precision math.
>
> So the ABI changed to make it soft-float and the libc (or libm) handle
> that deficiency in software if required, making old precompiled binaries
> incompatible (of no concern for buildroot since we've got no precompiled
> binary blobs for SPE in packages).
I'm not sure to fully understand: is PowerPC really using *soft-float*
as in all floating point operations are emulated in software? Or is it
a difference similar to the difference between hardfp and softfp on ARM
(both use the FPU and floating point instructions, it's only a
different ABI, where hardfp passes floating point arguments in floating
point registers, while softfp passes floating point arguments in
integer registers).
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-11 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 11:56 [Buildroot] [PATCH 1/2] powerpc/spe: tweak glibc/eglibc/uclibc combinations Gustavo Zacarias
2014-09-11 11:56 ` [Buildroot] [PATCH 2/2] arch/powerpc: default to soft-float for SPE ABI Gustavo Zacarias
2014-09-11 20:57 ` Thomas Petazzoni [this message]
2014-09-11 21:45 ` [Buildroot] [PATCH 1/2] powerpc/spe: tweak glibc/eglibc/uclibc combinations Gustavo Zacarias
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=20140911225715.70f88987@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox