All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: u497w7n9@umail.furryterror.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Why is -msoft-float used in Kernel compilation?
Date: Sun, 14 Feb 1999 22:10:52 +0100 (CET)	[thread overview]
Message-ID: <199902142110.WAA00523@piglet.cpu.lu> (raw)
In-Reply-To: <199902131436.JAA07672@linuxmaster.corel.eng>


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...

Any guru around?

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


[[ 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 ]]

  parent reply	other threads:[~1999-02-14 21:10 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 [this message]
1999-02-15  6:41   ` Troy Benjegerdes
1999-02-15 11:49     ` Gary Thomas

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=199902142110.WAA00523@piglet.cpu.lu \
    --to=mlan@cpu.lu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --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 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.