All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [oe-commits]	org.oe.dev	conf/machine/include/tune-ppc405.inc :	Move	TARGET_FPU =	"soft" to the tune file so its
Date: Mon, 29 Oct 2007 13:24:27 +0100	[thread overview]
Message-ID: <4725D0FB.1040204@student.utwente.nl> (raw)
In-Reply-To: <HOECLKEKOHLAMMGDLLBHEEJIMKAA.skoroneos@digital-opsis.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stelios Koroneos schreef:
> Although this is getting OT :)
> 
> Buidling with hardfloat for a cpu that does not have an fpu means that
> 1) You need to have a kernel that supports fp emulation (and actually
> provides correct fp results)
> 2) Have it enabled by default in OE
> 3) Be prepared to pay the processing penalty as every fp instruction is
> going to generate an exeption that needs to be handled by the kernel.

Right, that's how we have done it in OE for the ARMs without FPU for the
past 4 years. On ARM it's a 10x-50x slowdown, but still very popular,
i.e. debian/arm is still using hardfloat. I'm not saying it makes sense,
I'm saying that this is how it has been done for the past 4 years :)

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHJdD7MkyGM64RGpERAiYEAJ9o15AwGFUlIekx/CrlnqVfwhkKFgCgoN4N
7anBacFs+gt5jg0dRLl0aKg=
=BOhh
-----END PGP SIGNATURE-----



      reply	other threads:[~2007-10-29 12:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Ilkzv-0004qZ-Aq@linuxtogo.org>
2007-10-27 14:48 ` [oe-commits] org.oe.dev conf/machine/include/tune-ppc405.inc : Move TARGET_FPU = "soft" to the tune file so its Koen Kooi
2007-10-28  5:56   ` Stelios Koroneos
2007-10-29  9:57     ` Koen Kooi
2007-10-29 11:17       ` Stelios Koroneos
2007-10-29 12:24         ` Koen Kooi [this message]

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=4725D0FB.1040204@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /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.