[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug gas/30120] x87: fucomp assembled as fucom
From: |
jbeulich at suse dot com |
Subject: |
[Bug gas/30120] x87: fucomp assembled as fucom |
Date: |
Mon, 13 Feb 2023 17:05:38 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=30120
Jan Beulich <jbeulich at suse dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #3 from Jan Beulich <jbeulich at suse dot com> ---
(In reply to Michael Matz from comment #2)
> Came in with bd7828084 "x86: use ModR/M for FPU insns with operands".
>
> The proper Reg field of ModRM for the popping variant of fucom is '5' not
> '4'.
> So this:
>
> --- a/opcodes/i386-opc.tbl
> +++ b/opcodes/i386-opc.tbl
> @@ -651,7 +651,7 @@ fcompp, 0xded9, FP, NoSuf, {}
> fucom, 0xdd/4, i387, Modrm|NoSuf, { FloatReg }
> // alias for fucom %st(1)
> fucom, 0xdde1, i387, NoSuf, {}
> -fucomp, 0xdd/4, i387, Modrm|NoSuf, { FloatReg }
> +fucomp, 0xdd/5, i387, Modrm|NoSuf, { FloatReg }
> // alias for fucomp %st(1)
> fucomp, 0xdde9, i387, NoSuf, {}
> fucompp, 0xdae9, i387, NoSuf, {}
Would you mind simply committing your change?
> (didn't check the other insns touched by the patch)
I've just gone through using a pattern I didn't use when composing the change,
and I didn't find any other similar issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug gas/30120] New: x87: fucomp assembled as fucom, matz at suse dot de, 2023/02/13
- [Bug gas/30120] x87: fucomp assembled as fucom, matz at suse dot de, 2023/02/13
- [Bug gas/30120] x87: fucomp assembled as fucom, matz at suse dot de, 2023/02/13
- [Bug gas/30120] x87: fucomp assembled as fucom, matz at suse dot de, 2023/02/13
- [Bug gas/30120] x87: fucomp assembled as fucom,
jbeulich at suse dot com <=
- [Bug gas/30120] x87: fucomp assembled as fucom, matz at suse dot de, 2023/02/13
- [Bug gas/30120] x87: fucomp assembled as fucom, matz at suse dot de, 2023/02/13