9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sean Quinlan <seanq@research.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] p9/linux/fbsd compiler shootout
Date: Tue, 26 Feb 2002 11:07:19 -0500	[thread overview]
Message-ID: <3C7BB2B7.5287E965@research.bell-labs.com> (raw)
In-Reply-To: <807a8afd7bb1bf60ebcafe1adb3004b1@plan9.bell-labs.com>

8c does almost no registerisation for floating point.
The floating point stack is used as a stack; i.e. the code for 
	y = y + x
looks like

	FMOVD	y+-16(SP),F0

	FADDD	x+-8(SP),F0
	
FMOVDP	F0,y+-16(SP)


even in the inner loops.  If you care about floating point on the x86,
you have to use a compiler that tries to treat the x86 floating point
stack into a register file... this is not easy and even with a lot of effort
and large amounts of hardware assistance, x86 floating point is still
relatively slow.  As rob said, ken never did this... on machines where
the floating point unit uses a register file, ken does a lot better.

seanq

rob pike wrote:
> 
> > Rob, can you say more about what 8c's shortcomings are in
> > floating point?
> 
> Ken just didn't spend much time on it.  A fair bit of effort was spent
> on integer code for most of the architectures, including x86.  When
> you have finite time (unlike the GCC people, who have infinite people
> and forever to work on it, 8c was a one-man operation) you choose
> where to spend it.
> 
> -rob


  reply	other threads:[~2002-02-26 16:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 14:20 rob pike
2002-02-26 16:07 ` Sean Quinlan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-26 15:02 andrey mirtchovski
2002-02-26 16:02 ` Wilhelm B. Kloke
2002-02-26 18:00   ` splite
2002-02-26 16:04 ` Matt H
2002-03-04 10:04 ` Gaute B Strokkenes
2002-02-26 14:18 rob pike
2002-02-26 11:15 forsyth
2002-02-26  3:10 rob pike
2002-02-26 10:26 ` Thomas Bushnell, BSG
2002-02-26  3:05 andrey mirtchovski
2002-02-26 10:27 ` Thomas Bushnell, BSG
2002-02-26 10:27 ` Thomas Bushnell, BSG

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=3C7BB2B7.5287E965@research.bell-labs.com \
    --to=seanq@research.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).