From: "Arati Dikey" <AratiD@kpit.com>
To: <binutils@sources.redhat.com>
Subject: [PATCH] : SH Assembler generates incorrect opcode for PCMP instructions
Date: Wed, 30 Jan 2002 21:51:00 -0000 [thread overview]
Message-ID: <97AA06615400F34AB695F23CE3D42E9150B72D@sohm.kpit.com> (raw)
Hi !
The SH assembler generates incorrect opcodes for the parallel PCMP
instruction.
Basically, its last nibble is a copy of the previous instruction's
second nibble
when working in Big Endian format.
For example,
test.s
movs.w @-R5, A0
PCMP X0,Y0
generates opcodes
f5 70
f8 00 84 05
instead of
f8 00 84 00
The following patch corrects this. I have also verified that it does not
cause any
side effect on other DSP instructions.
Regards,
Arati Dikey
Changelog
2002-01-17 Arati Dikey <aratid@kpit.com>
tc-sh.c (assemble_ppi): Do not add reg_n value for PCMP
instructions
--- tc-sh.c.orig Thu Dec 6 11:34:18 2001
+++ tc-sh.c Thu Jan 17 16:41:28 2002
@@ -1769,7 +1769,10 @@ assemble_ppi (op_end, opcode)
if (field_b)
as_bad (_("multiple parallel processing specifications"));
field_b = ((opcode->nibbles[2] << 12) + (opcode->nibbles[3] <<
8)
- + (reg_x << 6) + (reg_y << 4) + reg_n);
+ + (reg_x << 6) + (reg_y << 4) );
+
+ if (strcmp (opcode->name, "pcmp") != 0)
+ field_b += reg_n;
break;
case PDC:
if (cond)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Free download of GNUSH tool chain for Hitachi's SH Series.
The following site also offers free support to European customers.
Read more at http://www.kpit.com/products/support.htm.
Latest version of GNUSH is released on Jan 1, 2002.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2002-01-31 5:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 21:51 Arati Dikey [this message]
2002-01-31 13:55 ` Nick Clifton
2002-06-14 8:07 ` Joern Rennecke
-- strict thread matches above, loose matches on Subject: below --
2002-01-17 6:09 [ PATCH] " Arati Dikey
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=97AA06615400F34AB695F23CE3D42E9150B72D@sohm.kpit.com \
--to=aratid@kpit.com \
--cc=binutils@sources.redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).