This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 3/6] x86: improve operand reversal


On Fri, Aug 3, 2018 at 12:08 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> 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.

Why do you change testcases of the .s suffix?

> 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?

A patch for disassembler is welcome.


-- 
H.J.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]