linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gary Thomas <gdt@linuxppc.org>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: linuxppc-dev@lists.linuxppc.org, u497w7n9@umail.furryterror.org,
	Michel Lanners <mlan@cpu.lu>
Subject: Re: Why is -msoft-float used in Kernel compilation?
Date: Mon, 15 Feb 1999 11:49:08 -0000 (GMT)	[thread overview]
Message-ID: <XFMail.990215114908.gdt@linuxppc.org> (raw)
In-Reply-To: <Pine.LNX.4.04.9902150025360.432-100000@narn.local.drgw.net>



On 15-Feb-99 Troy Benjegerdes wrote:
> 
> On Sun, 14 Feb 1999, Michel Lanners wrote:
> 
>> 
>> On  13 Feb, this message from Gavriel State echoed through cyberspace:
>> > 
>> > I can understand using -msoft-float if CONFIG__8xx is on,
>> > but why use it when compiling for 60x or 7x0 CPUs?
>> 
>> I've heard something about a 'no floiting point in kernel' rule, and
>> I've tried compiling without -msoft-float.... it does boot, but it's an
>> ugly sight... fp warning messages all over!
>> 
>> I have, however, never seen a clear explanation of why that rule
>> exists...
> 
> I'm not sure, but I believe it's an optimization to allow the kernel to
> not have to save floating point registers on every context switch.
> 

More importantly it is to keep GCC from trying to use FP registers to
do structure copies.  Without this option, GCC will try to use the FP
registers to perform high[er] performance copying of structures.  This
would mean that the kernel would have to save/restore some number of
FP registers on every context change, not just the switch from user
to kernel mode, because these registers are considered totally volatile
by the compiler.

------------------------------------------------------------------------
Gary Thomas                              |
email: gdt@linuxppc.org                  | "Fine wine is a necessity of
   ... opinions expressed here are mine  |        life for me"
       and no one else would claim them! |
                                         |      Thomas Jefferson
------------------------------------------------------------------------



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

      reply	other threads:[~1999-02-15 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-13 14:37 Why is -msoft-float used in Kernel compilation? Gavriel State
1999-02-13 16:19 ` Michael Meissner
1999-02-14 21:10 ` Michel Lanners
1999-02-15  6:41   ` Troy Benjegerdes
1999-02-15 11:49     ` Gary Thomas [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=XFMail.990215114908.gdt@linuxppc.org \
    --to=gdt@linuxppc.org \
    --cc=hozer@drgw.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    --cc=u497w7n9@umail.furryterror.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).