[Bug gas/29183] Inconsistent behaviors of Types with PTR operator

[jbeulich at suse dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=29183

--- Comment #1 from Jan Beulich <jbeulich at suse dot com> ---
I see only two choices: Make this an error (like MASM does), or accept it as we
do now (as e.g. TASM does). I'm strongly in favor of retaining current behavior
to avoid the anomaly of

    mov al, 1[eax]
    mov al, [1+eax]
    mov al, [eax+1]

all meaning the same but then out of

    mov al, byte[eax]
    mov al, [byte+eax]
    mov al, [eax+byte]

only the latter two being accepted. (Note that I do not see any room at all for
making a difference of whether "byte" and "[" are separated by whitespace.)

IOW the presence / absence of "ptr" really does have a meaning.

-- 
You are receiving this mail because:
You are on the CC list for the bug.