From: "Russell McGuire" <rmcguire@uwbt.com>
To: "'Dan Malek'" <dan@embeddedalley.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: GNU and Freescale MPC83xx / e300 core support?
Date: Tue, 7 Mar 2006 07:54:19 -0800 [thread overview]
Message-ID: <002b01c641ff$666ccc70$6405a8c0@absolut> (raw)
In-Reply-To: <50206c46cf7e37ede345eebf82ad6fbc@embeddedalley.com>
Thanks all...
The author of that comment humbly apologizes for his ineptitude on the FPU.
It would appear both cores have the same number of execution units, i.e. 5
So David, I guess in all this the only real difference seems to be the bus
architecture, raw clock speed, and perhaps a few new instructions. I checked
both manuals this morning and they do differ in some small ways.
* 603e, up to 4 instructions in the pipeline, only 3 being complete per
clock
* e300, up to 5 instructions in the pipeline, still only 3 being completed
or start per clock.
* Add/compare instructions are now executed in the IU unit instead of the
load/store unit. May be the same, but wasn't specific in earlier 603e
manuals.
* One more HID0 bit than G2, ability to interrupt based on cache parity
error
* new icbt instruction, instruction cache initialization
So there is a section inside the 8360E manual that outlines the specific
enhancements. "Features specific to the e300 core not present on the G2
processors follow:" Page 1-5.
So I guess my question is back up, does anyone know if an optimized compiler
would offer any noticeable performance enhancements in regards to these
changes? Other than the obvious instruction being added?
Thanks
-Russ
-----Original Message-----
From: Dan Malek [mailto:dan@embeddedalley.com]
Sent: Tuesday, March 07, 2006 4:33 AM
To: Russell McGuire
Cc: 'David Hawkins'; linuxppc-embedded@ozlabs.org
Subject: Re: GNU and Freescale MPC83xx / e300 core support?
On Mar 7, 2006, at 12:52 AM, Russell McGuire wrote:
> ..... The most obvious core difference is
> the Floating Point unit; the MPC8280, 603e or G2LE core had no floating
> point ability at all.
I just want to state for archive purposes this simply isn't true.
All of those processors had hardware FPUs. If you would take
a few seconds and read the product overviews for these parts,
you can make your own informed decision. The person you
are talking to doesn't seem to have all of the facts in order.
-- Dan
next prev parent reply other threads:[~2006-03-07 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1141693203.8543.linuxppc-embedded@ozlabs.org>
2006-03-07 1:57 ` GNU and Freescale MPC83xx / e300 core support? Russell McGuire
2006-03-07 2:26 ` David Hawkins
2006-03-07 5:52 ` Russell McGuire
2006-03-07 6:07 ` Kumar Gala
2006-03-07 12:33 ` Dan Malek
2006-03-07 15:54 ` Russell McGuire [this message]
2006-03-07 16:03 ` Kumar Gala
2006-03-07 18:11 ` Kim Phillips
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='002b01c641ff$666ccc70$6405a8c0@absolut' \
--to=rmcguire@uwbt.com \
--cc=dan@embeddedalley.com \
--cc=linuxppc-embedded@ozlabs.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.