public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Joern Rennecke <joern.rennecke@superh.com>
To: Nick Clifton <nickc@cambridge.redhat.com>
Cc: AratiD@kpit.com, amylaar@onetel.net.uk, hp@bitrange.com,
	binutils@sources.redhat.com
Subject: Re: [PATCH] : SH Assembler generates incorrect opcode for PCMP  instructions
Date: Fri, 14 Jun 2002 08:07:00 -0000	[thread overview]
Message-ID: <3D0A067C.885220A9@superh.com> (raw)
In-Reply-To: <m3g04murnk.fsf@north-pole.nickc.cambridge.redhat.com>

Nick Clifton wrote:
> 
> Hi Arati,
> 
> > 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.

That's not exactly incorrect, since the reg_n field for pcmp is
ignored by the CPU.

> Your patch does work, but I do not like the way it makes a special
> case out of the opcode's name.  In fact I think that it may not be
> just the PCMP instruction that has this problem, since a perusal of
> the sh-opc.h file indicates that the PABS and PRND instructions may
> also have similar difficulties.

No, PCMP is indeed special, since it is the only PPI3 instuction that
ignores REG_N.

Moreover, REG_X and REG_Y are initialized at the start of assemble_ppi.

To get non-varying opcodes for pcmp, you can clear reg_n at that point, too.
	
-- 
--------------------------
SuperH
2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ
T:+44 1454 462330

  reply	other threads:[~2002-06-14 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 21:51 Arati Dikey
2002-01-31 13:55 ` Nick Clifton
2002-06-14  8:07   ` Joern Rennecke [this message]
  -- 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=3D0A067C.885220A9@superh.com \
    --to=joern.rennecke@superh.com \
    --cc=AratiD@kpit.com \
    --cc=amylaar@onetel.net.uk \
    --cc=binutils@sources.redhat.com \
    --cc=hp@bitrange.com \
    --cc=nickc@cambridge.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).