All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista.com>
To: clark@esteem.com,
	Navin Boppuri <nboppuri@trinetcommunication.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Differences between MPC823 powerpc & any other powerpc
Date: Mon, 11 Sep 2000 10:51:23 -0700	[thread overview]
Message-ID: <39BD1B9B.1729B5B@mvista.com> (raw)
In-Reply-To: 1.5.4.32.20000911170434.006a51e8@pop.esteem.com


clark@esteem.com wrote:
>
> At 11:48 AM 5/12/00 +0100, you wrote:
> >
> >Hello,
> >
> >I would like to know what are the basic difference between the MPC823
> >PowerPC and any other PowerPC , say, the G4? Why dont the binaries running
> >on G4 not work correctly on the MPC823?
>
>         For starters the MPC823 has no FPU. I think you could compile FPU
> emulation into the kernel to remedy this but I'm not sure. G4 compiled
> programs may use alti-vec instructions but I'm not sure on this either.
>

In addition to no FPU, the 8xx series also has half of the cachelines
that all
of the other PPC's have.  (4xx, 6xx, 7xx, 74xx, 82xx)  This causes a
problem
with glibc [and possibly other things] which expect a certain line size
to do
fast memset's, memcpy's etc.  (The result of having the wrong cacheline
size
is to miss area's of memory in the previous listed functions.)

Also w/ the no FPU comes ABI issues including (especially?) var args
issues.

--Mark

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-09-11 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-11 17:04 Differences between MPC823 powerpc & any other powerpc clark
2000-09-11 17:51 ` Mark Hatle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-11 16:44 Navin Boppuri
2000-09-11 19:54 ` Dan Malek

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=39BD1B9B.1729B5B@mvista.com \
    --to=fray@mvista.com \
    --cc=clark@esteem.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=nboppuri@trinetcommunication.com \
    /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.