linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "kim sook young" <icekim@sec.samsung.co.kr>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Error: Unrecognized opcode
Date: Wed, 10 May 2000 14:24:40 +0900	[thread overview]
Message-ID: <000501bfba40$0dd50200$efc5dba8@sec.samsung.co.kr> (raw)


hi,all

While compiling, Some weird messages occurred.
I  don't think rorw is available opcode on the ppc environment. do i?
I don't know why rorw opcodes are generated in assembly code.

----------------------------------------------------------------
Compiling smbd/oplock.c
/tmp/ccs9oFVa.s: Assembler messages:
/tmp/ccs9oFVa.s:190: Error: Unrecognized opcode: `rorw'
/tmp/ccs9oFVa.s:414: Error: Unrecognized opcode: `rorw'
/tmp/ccs9oFVa.s:417: Error: Unrecognized opcode: `rorw'
/tmp/ccs9oFVa.s:1171: Error: Unrecognized opcode: `rorw'
/tmp/ccs9oFVa.s:2629: Error: Unrecognized opcode: `rorw'
make: *** [smbd/oplock.o] Error 1

---------------------------------------------------------------
the following is a part of the assembly code.

.L199:
        lis 9,global_oplock_port@ha
        la 9,global_oplock_port@l(9)
        lhz 0,10(1)
        rorw $8, 0
        sth 0,0(9)
        bl setup_kernel_oplock_pipe
        cmpwi 0,3,0
        bc 4,2,.L203
        li 3,0
        b .L205
----------------------------------------------------------------

I hope somebody would tip me off to the solution(?)

Thanks
regards


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

                 reply	other threads:[~2000-05-10  5:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='000501bfba40$0dd50200$efc5dba8@sec.samsung.co.kr' \
    --to=icekim@sec.samsung.co.kr \
    --cc=linuxppc-embedded@lists.linuxppc.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).