linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@cygnus.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: cc/gcc/egcs kernel compilation options?
Date: Thu, 8 Jul 1999 07:17:00 -0400	[thread overview]
Message-ID: <19990708071700.A21166@tiktok.cygnus.com> (raw)
In-Reply-To: <19990707130317.A21114@drow.res.cmu.edu>; from Daniel Jacobowitz on Wed, Jul 07, 1999 at 01:03:17PM -0400


On Wed, Jul 07, 1999 at 01:03:17PM -0400, Daniel Jacobowitz wrote:
> 
> On Thu, Jul 01, 1999 at 10:49:57PM +0000, Barrie Spence wrote:
> > 
> > As a PPC newbie, why do we need/use "-msoft-float"? Is this 
> > to handle some processor implementations that don't have 
> > floating-point hardware? (and if so, does it have any overhead 
> > on the 603/604/G3 Macs?). If it does have some cost, could it 
> > not be enabled in the same way as on Intel?
> > 
> > Next question, is there any advantage to building a kernel
> > with "-mcpu=604 -mtune=604"? (or whatever is most appropriate).
> 
> Floating point operations in the kernel are pretty rare, and thus do
> not need to be optimized for speed; soft-float is thus acceptable.  The
> advantage is that we don't need to save/restore the FPU registers and
> state nearly as often.  And I do not know why x86 does not have this
> issue.

The -msoft-float is there to prevent the compiler from converting some double
word moves into load floating/store floating combination.  The x86 compiler
does not allow values with integer modes (QImode, HImode, SImode, etc.) in fp
registers.  The powerpc can't do that since it would break int<->fp
conversions.

-- 
Michael Meissner, Cygnus Solutions
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886
email: meissner@cygnus.com	phone: 978-486-9304	fax: 978-692-4482

[[ 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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

      reply	other threads:[~1999-07-08 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01 22:49 cc/gcc/egcs kernel compilation options? Barrie Spence
1999-07-02  1:05 ` Anirudh Joshi
1999-07-07 17:03 ` Daniel Jacobowitz
1999-07-08 11:17   ` Michael Meissner [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=19990708071700.A21166@tiktok.cygnus.com \
    --to=meissner@cygnus.com \
    --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).