All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pantelis Antoniou <panto@intracom.gr>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: [OT?] Unimplemented instructions on a G5?
Date: Mon, 05 Apr 2004 09:05:16 +0300	[thread overview]
Message-ID: <4070F71C.80201@intracom.gr> (raw)
In-Reply-To: <200404021549.i32FnZT35302@makai.watson.ibm.com>


David Edelsohn 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.
>>>
>>>
>
>
>
>>>>>>Segher Boessenkool writes:
>>>>>>
>>>>>>
>Segher> Well, the newest PowerPC architecture docs say that it is
>Segher> an optional insn, i.e., not all cpus might implement it.
>
>Segher> I can't say whether the 970 implements it or not.
>
>	mcrxr is obsolete and not implemented in PPC970.  Executing the
>instruction will result in an illegal instruction trap.
>
>David
>
>
>
Well this much is obvious. Where can I find a list
of these obsolete instructions so that I can
implement them in the illegal instruction handler?

The IBM documentation for the 970 declares these instructions
as the previous architecture papers, i.e. as nothing special.

Regards

Pantelis


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

  reply	other threads:[~2004-04-05  6:05 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 [this message]
2004-04-05  6:14   ` Pantelis Antoniou

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=4070F71C.80201@intracom.gr \
    --to=panto@intracom.gr \
    --cc=dje@watson.ibm.com \
    --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 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.