From: Ian Lance Taylor <ian@cygnus.com>
To: jeffdb@goodnet.com
Cc: gas2@cygnus.com
Subject: Re: Question re fstsww fstcww fnstsww && fldcww i386pei /* note RETURN address */
Date: Sun, 06 Dec 1998 10:24:00 -0000 [thread overview]
Message-ID: <199812061824.NAA06551@subrogation.cygnus.com> (raw)
In-Reply-To: <36670e45.1065414@mail.goodnet.com>
From: jeffdbREMOVETHIS@goodnet.com (Mikey)
Date: Thu, 03 Dec 1998 22:28:41 GMT
is there a reason that support was dropped
for these instructions, or to put it another way
that the size suffix is no longer recognized?
my binutils is 980705, so this may have been
fixed in more recent. ;^)
#define fstsww fstsw
#define fstcww fstcw
#define fnstsww fnstsw
#define fldcww fldcw
Although the size suffix is redundant for these instructions, I can't
think of any reason that gas should reject it. I checked in the
appended patch.
Ian
Index: i386.h
===================================================================
RCS file: /cvs/cvsfiles/devo/include/opcode/i386.h,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -r1.66 -r1.67
--- i386.h 1998/11/11 05:58:08 1.66
+++ i386.h 1998/12/06 18:22:56 1.67
@@ -674,15 +674,15 @@
/* processor control */
{"fninit", 0, 0xdbe3, X, FP, { 0, 0, 0} },
{"finit", 0, 0xdbe3, X, FP|FWait, { 0, 0, 0} },
-{"fldcw", 1, 0xd9, 5, FP|Modrm, { ShortMem, 0, 0} },
-{"fnstcw", 1, 0xd9, 7, FP|Modrm, { ShortMem, 0, 0} },
-{"fstcw", 1, 0xd9, 7, FP|FWait|Modrm, { ShortMem, 0, 0} },
-{"fnstsw", 1, 0xdfe0, X, FP, { Acc, 0, 0} },
-{"fnstsw", 1, 0xdd, 7, FP|Modrm, { ShortMem, 0, 0} },
-{"fnstsw", 0, 0xdfe0, X, FP, { 0, 0, 0} },
-{"fstsw", 1, 0xdfe0, X, FP|FWait, { Acc, 0, 0} },
-{"fstsw", 1, 0xdd, 7, FP|FWait|Modrm, { ShortMem, 0, 0} },
-{"fstsw", 0, 0xdfe0, X, FP|FWait, { 0, 0, 0} },
+{"fldcw", 1, 0xd9, 5, w_Suf|IgnoreSize|Modrm, { ShortMem, 0, 0} },
+{"fnstcw", 1, 0xd9, 7, w_Suf|IgnoreSize|Modrm, { ShortMem, 0, 0} },
+{"fstcw", 1, 0xd9, 7, w_Suf|IgnoreSize|FWait|Modrm, { ShortMem, 0, 0} },
+{"fnstsw", 1, 0xdfe0, X, w_Suf|IgnoreSize, { Acc, 0, 0} },
+{"fnstsw", 1, 0xdd, 7, w_Suf|IgnoreSize|Modrm, { ShortMem, 0, 0} },
+{"fnstsw", 0, 0xdfe0, X, w_Suf|IgnoreSize, { 0, 0, 0} },
+{"fstsw", 1, 0xdfe0, X, w_Suf|IgnoreSize|FWait, { Acc, 0, 0} },
+{"fstsw", 1, 0xdd, 7, w_Suf|IgnoreSize|FWait|Modrm, { ShortMem, 0, 0} },
+{"fstsw", 0, 0xdfe0, X, w_Suf|IgnoreSize|FWait, { 0, 0, 0} },
{"fnclex", 0, 0xdbe2, X, FP, { 0, 0, 0} },
{"fclex", 0, 0xdbe2, X, FP|FWait, { 0, 0, 0} },
/* Short forms of fldenv, fstenv use data size prefix.
prev parent reply other threads:[~1998-12-06 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-03 14:36 Mikey
1998-12-06 10:24 ` Ian Lance Taylor [this message]
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=199812061824.NAA06551@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=gas2@cygnus.com \
--cc=jeffdb@goodnet.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).