From: "Gavriel State" <u497w7n9@umail.furryterror.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Why is -msoft-float used in Kernel compilation?
Date: Sat, 13 Feb 1999 09:37:46 -0500 [thread overview]
Message-ID: <199902131436.JAA07672@linuxmaster.corel.eng> (raw)
I can understand using -msoft-float if CONFIG__8xx is on,
but why use it when compiling for 60x or 7x0 CPUs?
-Gav
--
Gavriel State
Engineering Project Leader - Linux Apps
Corel Corp
gavriels@corel.com
[[ 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 ]]
next reply other threads:[~1999-02-13 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-13 14:37 Gavriel State [this message]
1999-02-13 16:19 ` Why is -msoft-float used in Kernel compilation? Michael Meissner
1999-02-14 21:10 ` Michel Lanners
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=199902131436.JAA07672@linuxmaster.corel.eng \
--to=u497w7n9@umail.furryterror.org \
--cc=linuxppc-dev@lists.linuxppc.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).