From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: "Patrick J. Kelsey" <KelseyPJ@fairmountautomation.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Can 750 user-mode binaries run on a 603e core?
Date: Thu, 27 Jul 2006 08:36:00 -0400 [thread overview]
Message-ID: <44C8B330.7030600@smiths-aerospace.com> (raw)
In-Reply-To: <A958F7B12F59EC408E904A912CDE3DAE3D6A0A@cvn68.fairmountautomation.com>
Patrick J. Kelsey wrote:
> (sorry about that last one. had a bit of trouble with a certain web based mail client...)
>
> Thanks for the reply, Kumar.
>
> That sounds encouraging. One of the things I was worried about with
> scheduling differences would be a differing number of branch delay
> slots between the two core versions. I'm still a bit new to the
> details of the PowerPC architecture, and at this point I'm not even
> sure if there are branch delay slots, although it does seem from my
> reading that the 603e and 750 pipelines are the same, in which case
> there would ceratinly be no worries here.
FWIIW, the PowerPC architecture has hardware instruction interlocking
and scheduling and doesn't require the compiler to implement the branch
delay slots like, for instance, the MIPS architecture. This is much
more compiler and portability friendly, but at the expense of more logic
in the processor (the PowerPC is not nearly as minimalistic as the MIPS).
> At this point, I'm not concerned so much about an inefficient
> schedule resulting from running -mcpu=750 code on a 603e as long as
> the execution is correct.
>
> Pat
gvb
next prev parent reply other threads:[~2006-07-27 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 22:27 Can 750 user-mode binaries run on a 603e core? Patrick J. Kelsey
2006-07-27 0:04 ` Kumar Gala
2006-07-27 2:53 ` Patrick J. Kelsey
2006-07-27 3:53 ` Patrick J. Kelsey
2006-07-27 11:27 ` Matt Sealey
2006-07-27 12:18 ` Patrick J. Kelsey
2006-07-27 12:36 ` Jerry Van Baren [this message]
2006-07-27 15:30 ` Andy Fleming
2006-07-27 15:37 ` Kumar Gala
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=44C8B330.7030600@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=KelseyPJ@fairmountautomation.com \
--cc=linuxppc-dev@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 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).