From: Stefan Reinauer <stepan@openbios.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [ppc patch] soft-float
Date: Thu, 7 Oct 2004 16:54:30 +0200 [thread overview]
Message-ID: <20041007145430.GA25114@openbios.org> (raw)
In-Reply-To: <200410071118.13954.okuji@enbug.org>
* Yoshinori K. Okuji <okuji@enbug.org> [041007 11:18]:
> On Wednesday 06 October 2004 12:18, Tomas Ebenlendr wrote:
> > This can be done with integers, if we define some 'human big number
> > format', or so. But I think that FP/FPE is more generic problem,
> > because of modularity of grub.
In case of file sizes, the number format is just bytes..
(bytes>>10) is kbytes
etc... It is easy to shift through and print the remainder..
> But, IMO, floating point is not required for boot loaders. I admit that
> floating point is convenient, but I don't see many cases where floating
> point is useful in the context of boot loaders.
If a module wants to use fp, it should take care of checking for an fpu
and enabling it autonomously. There's cases where operating
systems started crashing because they assumed that the fpu is untouched
at a certain point of startup. Sure, it's the OSes fault to some regard.
But we don't start enabling MMU and paging either. Even though some
applications might use it. At some point it is the responsibility of an
OS or standalone application to handle hardware extensions. And this
point should not be pushed higher for no real reason.
Stefan
prev parent reply other threads:[~2004-10-07 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-03 23:46 [ppc patch] soft-float Hollis Blanchard
2004-10-04 11:24 ` Marco Gerards
2004-10-06 7:10 ` Stefan Reinauer
2004-10-06 8:57 ` Yoshinori K. Okuji
2004-10-06 9:59 ` Marco Gerards
2004-10-06 10:18 ` Tomas Ebenlendr
2004-10-07 9:18 ` Yoshinori K. Okuji
2004-10-07 14:54 ` Stefan Reinauer [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=20041007145430.GA25114@openbios.org \
--to=stepan@openbios.org \
--cc=grub-devel@gnu.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.