All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: annamaya <annamaya@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8xx binaries running on a MPC82xx board
Date: Tue, 9 Nov 2004 12:16:46 -0500	[thread overview]
Message-ID: <22B5F92B-3273-11D9-8E74-003065F9B7DC@embeddededge.com> (raw)
In-Reply-To: <20041109163726.30776.qmail@web53808.mail.yahoo.com>


On Nov 9, 2004, at 11:37 AM, annamaya wrote:

> I was under the assumption that the MPC8xx core was
> different from the MPC82xx core (the 603e?).

Yes, it is different, but the instructions are all the same.

> ...... But I was
> surprised to find that the MPC8xx binaries were
> running fine on a MPC82xx binaries, even if they were
> dynamically linked and were linking to the MPC82xx
> libraries. What's going on here?

Partly luck, and partly that the instructions are the same.
The luck part is you aren't using floating point.  The 8xx
doesn't have hardware floating point, but the 82xx generated
code may have some instructions.  It also depends upon
the tools you are using.  If you were using different glibc
versions, your luck would have run out.

 From a user space application perspective, there are
exactly two differences between 8xx and 82xx.  One is
floating point and the other is cache line size.  The 8xx
software will run fine on the 82xx, but 82xx may not
work properly on 8xx.

> ...... Can I just use the
> 8xx toolkit to work with the 82xx?

An 8xx toolkit will always work on 82xx, but depending
upon the way it was built, you will not get the maximum
performance of the 82xx.  Some tool vendors generate
toolkits (and libraries) specifically for the 8xx, where the
floating point is all emulated in software.  If you were looking
for floating point performance, you would be very disappointed
with this on the 82xx.

> ....... There must be SOME
> differences between these two architectures. Can
> someone here explain this to me?

There are lots of differences in the kernel programming
model, but only the two I mentioned for user space
applications.  In fact, across the entire PowerPC architecture
you will only see floating point, Altivec, SPE, and some
cache line operation/implementation differences at
the user level.  Depending upon your software
requirements and implementation, you are likely
able to run many of the same binaries across all
of the PowerPC cores.

I guess we are rewriting the archives now? :-)


	-- Dan

  parent reply	other threads:[~2004-11-09 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09 16:37 MPC8xx binaries running on a MPC82xx board annamaya
2004-11-09 16:50 ` Kumar Gala
2004-11-09 17:16 ` Dan Malek [this message]
2004-11-09 17:30   ` annamaya
2004-11-09 18:36     ` Dan Malek
2004-11-09 19:01       ` annamaya

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=22B5F92B-3273-11D9-8E74-003065F9B7DC@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=annamaya@yahoo.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.