From: "Timothy A. Seufert" <tas@mindspring.com>
To: Giuliano Pochini <pochini@shiny.it>, linuxppc-dev@lists.linuxppc.org
Subject: Re: [OT] 7450
Date: Mon, 12 Mar 2001 21:56:46 -0800 [thread overview]
Message-ID: <v04220801b6d361120d09@[10.0.0.42]> (raw)
In-Reply-To: <XFMail.010312125719.pochini@shiny.it>
At 12:57 PM +0100 3/12/01, Giuliano Pochini wrote:
>>But with five cycles of FP latency, scheduling becomes really important.
>
>Hmm, probably soft compiled for 604 runs fine on 7450 because it had
>similar latencies and a 6-stage pipeline.
The 604 has a 3-stage FPU, same as just about every other PPC Apple
has used. The 7450 has a 5-stage FPU.
Tim Seufert
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-13 5:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 11:57 [OT] 7450 Giuliano Pochini
2001-03-13 5:56 ` Timothy A. Seufert [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-09 8:59 Giuliano Pochini
2001-03-09 19:08 ` Dan Malek
2001-03-10 15:15 ` Holger Bettag
2001-03-11 1:43 ` David Edelsohn
2001-03-15 13:05 ` Holger Bettag
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='v04220801b6d361120d09@[10.0.0.42]' \
--to=tas@mindspring.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@shiny.it \
/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).