From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] BB update Was: Build jobbing
Date: Sun, 29 Nov 2009 05:23:09 -0600 [thread overview]
Message-ID: <200911290523.11206.minimod@morethan.org> (raw)
In-Reply-To: <200911290453.34368.minimod@morethan.org>
On Sun November 29 2009, Michael S. Zick wrote:
>
> Between the configuration menu/matrix and the runtime cpuid thingy -
> I expect I can get this system to turn out something better than 1984 MIPS code.
>
Dream on. . .
First footnote of interest found:
"Floating-point operations on very small numbers (denormalized numbers) and illegal
numbers (NaNs) must be handled by software. Also some IEEE exceptions and exceptional
results will cause an FPU exception. The FPU emulator is thus mandatory for full IEEE
compliance, ___even when the system has a hardware FPU___."
Emphasis added.
So we can't configure with a simple:
soft-float / hard-float configuration variable - -
the choices are: soft-float / sort-of-hard-float + a bit of help.
That will also impact that "help message" about not loading the FPU emulator into
a kernel more recent than 1997....
If your running MIPS, and your core has hardware floating point and you choose:
hard-float - - you still need the FPU emulator loaded for IEEE compliance.
Translation: the FPU emulator is not optional, you need it regardless of the
hard-float / soft-float selection.
I guess we have to go all the way back to the uClibc question:
"does your machine have an FPU?" yes/no
to
"does your machine have an FPU?" yes/sort-of/no
Just in case I needed a reminder of why I retired from this *&^&*% twenty years ago.
As if I need another one. ;)
Mike
next prev parent reply other threads:[~2009-11-29 11:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 21:22 [Buildroot] Build jobbing Michael S. Zick
2009-11-27 21:56 ` Peter Korsgaard
2009-11-27 22:10 ` Michael S. Zick
2009-11-27 22:16 ` Michael S. Zick
2009-11-27 22:33 ` Michael S. Zick
2009-11-27 22:45 ` Michael S. Zick
2009-11-27 22:59 ` Michael S. Zick
2009-11-28 10:40 ` Peter Korsgaard
2009-11-28 10:45 ` Peter Korsgaard
2009-11-28 11:10 ` Michael S. Zick
2009-11-28 11:38 ` Michael S. Zick
2009-11-28 18:58 ` Michael S. Zick
2009-11-28 14:07 ` Peter Korsgaard
2009-11-28 14:13 ` Michael S. Zick
2009-11-28 15:35 ` [Buildroot] BB update Was: " Michael S. Zick
2009-11-28 15:43 ` Michael S. Zick
2009-11-28 19:06 ` Peter Korsgaard
2009-11-28 19:15 ` Michael S. Zick
2009-11-28 19:20 ` Peter Korsgaard
2009-11-28 19:06 ` Peter Korsgaard
2009-11-28 19:17 ` Michael S. Zick
2009-11-28 19:41 ` Michael S. Zick
2009-11-28 20:30 ` Peter Korsgaard
2009-11-28 21:16 ` Michael S. Zick
2009-11-28 22:44 ` Peter Korsgaard
[not found] ` <200911281650.44375.minimod@morethan.org>
[not found] ` <87r5rh3e8w.fsf@macbook.be.48ers.dk>
2009-11-29 9:16 ` Michael S. Zick
[not found] ` <200911290302.13984.minimod@morethan.org>
[not found] ` <87my253d8o.fsf@macbook.be.48ers.dk>
2009-11-29 9:31 ` Michael S. Zick
2009-11-29 10:23 ` Peter Korsgaard
2009-11-29 10:53 ` Michael S. Zick
2009-11-29 11:23 ` Michael S. Zick [this message]
2009-11-29 12:54 ` Michael S. Zick
2009-11-29 16:50 ` Michael S. Zick
2009-11-29 18:11 ` Michael S. Zick
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=200911290523.11206.minimod@morethan.org \
--to=minimod@morethan.org \
--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