[PATCH 3/6] x86: improve operand reversal
Jan Beulich
JBeulich@suse.com
Fri Aug 3 07:08:00 GMT 2018
More information about the Binutils mailing list
Fri Aug 3 07:08:00 GMT 2018
- Previous message (by thread): [PATCH 3/6] x86: improve operand reversal
- Next message (by thread): [PATCH 3/6] x86: improve operand reversal
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>>> On 02.08.18 at 18:43, <hjl.tools@gmail.com> wrote: > Please don't make any changes to the deprecated ".s". Excuse me, but how many more times should I state that I don't make any changes to its behavior? I solely make {store} no longer match .s in behavior. In fact I've specifically undone the change to .s, in anticipation of your objection to any adjustment to it. And btw - it's nice to have all these pseudo prefixes, if only they had actually worked half way correctly from the very beginning. And I'm already leaving aside the case of the indeed non-trivial situation with {,v}movq, where there are two load and two store encodings available in 64-bit mode (when there's a memory operand). I would expect to be able to control this as a programmer, but I have no good idea on how to make this work. Furthermore, and I'm sorry to say that, but something like {disp32} was ill-advised altogether (just like the now deprecated .d32): It's at best confusing for 16-bit addressing. This should have been e.g. {dispw}. But that ship has sailed now. Additionally - if .s is deprecated, why does the disassembler continue to emit it? Jan
- Previous message (by thread): [PATCH 3/6] x86: improve operand reversal
- Next message (by thread): [PATCH 3/6] x86: improve operand reversal
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list