public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Jerry Quinn" <jquinn@nortelnetworks.com>
To: law@cygnus.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: PATCH: minor hppa disasm cleanup
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <376802F6.B6FBAE0F@americasm01.nt.com> (raw)
In-Reply-To: <1127.929431269@upchuck.cygnus.com>

Jeffrey A Law wrote:
> 
>   In message < 199906011505.LAA08672@wmtl249c.us.nortel.com >you write:
>   > In the pa disassembler, the 'E' code is always used for 0x0C opcodes
>   > where only left register halves occur.  So the L/R selection bit at 25
>   > is always 0 and the test isn't required.
>   >
>   > This is patched against 990413, since I can't use cvs to update my
>   > snapshot (restrictive firewall) and this is the last one I have.
>   >
>   > Changelog entry:
>   >
>   > Tue Jun  1 11:03:02 EDT 1999  Jerry Quinn <jquinn@nortelnetworks.com>
>   >
>   >     * hppa-dis.c (print_insn_hppa): Remove unnecessary test in 'E'
>   >       code.
> Is this really correct?  Consider xmpyu, fmpyfadd & fmpynfadd, none of which
> are 0xc opcodes, but all use 'E'

I think the 'E' code in these three instructions is incorrect.  The
disassembler considers E to be 6:10,25 while J is 6:10,24.  In the
assembler, the templates with 'J' are never used at all.  Instead, the
template with 'E' detects if there is an R float reg and then flips the
opcode from 0xc to 0xe.  It just happens that that opcode flip is safe
and does nothing for these three instructions.

My feeling for how it should work is that E is a left half float reg
code only.  When that fails, the compiler would try to use the J
template and succeed.  Also, the change from pa10 to pa11 could be
handled by the J templates being pa11 while E templates are pa10.

If that sounds OK, I'll see if I can find some time to reorganize the
code.

Jerry


-- 
Jerry Quinn                             Tel: (514) 761-8737
jquinn@nortelnetworks.com               Fax: (514) 761-8505
Speech Recognition Research

  reply	other threads:[~1999-07-01  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-01  0:00 Jerry Quinn
1999-07-01  0:00 ` Jeffrey A Law
1999-07-01  0:00   ` Jerry Quinn [this message]
1999-07-28  3:42     ` Jeffrey A Law

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=376802F6.B6FBAE0F@americasm01.nt.com \
    --to=jquinn@nortelnetworks.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=law@cygnus.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).