From: Doug Evans <dje@canuck.cygnus.com>
To: gas2@canuck.cygnus.com
Subject: i386-dis.c OP_OFF patch
Date: Mon, 03 Jun 1996 16:27:00 -0000 [thread overview]
Message-ID: <199606032327.QAA08613@canuck.cygnus.com.> (raw)
Objdump is incorrectly disassembling this insn:
mov %fs:0,%eax
`%fs:' is not printed.
I don't know the 386 well enough, but does this look right?
Mon Jun 3 16:17:25 1996 Doug Evans <dje@canuck.cygnus.com>
* i386-dis.c (OP_OFF): Call append_prefix.
Index: i386-dis.c
===================================================================
RCS file: /cvs/cvsfiles/devo/opcodes/i386-dis.c,v
retrieving revision 1.19
diff -c -p -r1.19 i386-dis.c
*** i386-dis.c 1996/02/20 16:08:02 1.19
--- i386-dis.c 1996/06/03 23:14:13
*************** OP_OFF (bytemode)
*** 1939,1945 ****
int bytemode;
{
int off;
!
if (aflag)
off = get32 ();
else
--- 1939,1947 ----
int bytemode;
{
int off;
!
! append_prefix ();
!
if (aflag)
off = get32 ();
else
reply other threads:[~1996-06-03 16:27 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=199606032327.QAA08613@canuck.cygnus.com. \
--to=dje@canuck.cygnus.com \
--cc=gas2@canuck.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).