[PATCH v2 5/9] x86: improve handling of insns with ambiguous operand sizes
H.J. Lu
hjl.tools@gmail.com
Thu Nov 14 19:19:00 GMT 2019
More information about the Binutils mailing list
Thu Nov 14 19:19:00 GMT 2019
- Previous message (by thread): [PATCH v2 5/9] x86: improve handling of insns with ambiguous operand sizes
- Next message (by thread): [PATCH v2 5/9] x86: improve handling of insns with ambiguous operand sizes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Nov 14, 2019 at 1:00 AM Jan Beulich <jbeulich@suse.com> wrote: > > On 13.11.2019 22:12, H.J. Lu wrote: > > What do you mean by improving AT&T syntax? AT&T syntax has > > many quirks. We should leave them alone if we can. > > May I kindly ask you to read the description of this patch again. > Current AT&T behavior is, as far as I'm concerned, intolerably > dangerous (and in the course of putting together this change > over the last couple of years it has helped point out actual > mistakes in other projects that I've been building with early > versions of this change in place). > The default size is one of quirks. Changing it can make previously working assembly codes stop working. If one is writing the new assembly codes in AT&T syntax, she/he should avoid default size when in doubt. We can add a command-line switch to check these quirks. -- H.J.
- Previous message (by thread): [PATCH v2 5/9] x86: improve handling of insns with ambiguous operand sizes
- Next message (by thread): [PATCH v2 5/9] x86: improve handling of insns with ambiguous operand sizes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list