linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [OT?] Unimplemented instructions on a G5?
Date: Mon, 05 Apr 2004 09:14:16 +0300	[thread overview]
Message-ID: <4070F938.5010204@intracom.gr> (raw)
In-Reply-To: <EC443756-84BA-11D8-89ED-000A95A4DC02@kernel.crashing.org>


Segher Boessenkool wrote:

>
>> The offending instruction is the seemingly harmless:
>>
>>  mcrxr crX
>>
>>   (Move to condition register from XER).
>>
>> Does anyone have any idea if IBM left this instruction
>> unimplemented. Searching the docs I've found nothing.
>
>
> Well, the newest PowerPC architecture docs say that it is
> an optional insn, i.e., not all cpus might implement it.
>
> I can't say whether the 970 implements it or not.
>
> http://www-106.ibm.com/developerworks/eserver/pdfs/archpub1.pdf
> Chapter 6.
>
Thanks this was the information I needed. Actually it's only
the mcrxr instruction that's unimplemented. Just my luck :-)

>> If it is unimplemented any idea of how hard it will be to
>> trap and emulate it?
>
>
> In Linux?
>
> Last time I did this, it was easy.  Can't seem to find the
> patch right now, though.
>
> Emulating will be slow, of course (but I think you know that).
>
>
> Segher
>
>
>
>
>
Regards

Pantelis


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

      parent reply	other threads:[~2004-04-05  6:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 13:51 [OT?] Unimplemented instructions on a G5? Pantelis Antoniou
2004-04-02 15:32 ` Segher Boessenkool
2004-04-02 15:49   ` David Edelsohn
2004-04-05  6:05     ` Pantelis Antoniou
2004-04-05  6:14   ` Pantelis Antoniou [this message]

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=4070F938.5010204@intracom.gr \
    --to=panto@intracom.gr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=segher@kernel.crashing.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).