[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug gas/21874] x86: Multiple segment registers in the address are not d
From: |
jbeulich at novell dot com |
Subject: |
[Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel |
Date: |
Fri, 10 Nov 2017 12:58:20 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=21874
--- Comment #9 from Jan Beulich <jbeulich at novell dot com> ---
(In reply to H.J. Lu from comment #8)
> (In reply to Jan Beulich from comment #7)
> > (In reply to H.J. Lu from comment #6)
> > > If gas doesn't allow multiple segment registers in AT&T syntax, it
> > > shouldn't allow them in Intel syntax.
> >
> > I can only keep telling you that I view maximum possible compatibility with
> > MASM more important that compatibility between the under-specified (or
> > should I say not specified at all) AT&T syntax. As the maintainer of the
> > Intel syntax code I would not have approved the patch in the shape you've
> > committed it. Please fix it to avoid the need to revert.
>
> My understanding is that gas can't assemble many assembly codes which
> accept MASM.
Of course, hence me saying "maximum possible compatibility" (instead of saying
"full").
> It is more important for gas to be consistent with itself.
That's a bogus goal imo: Different assembly syntax can naturally result in
apparent inconsistencies.
> In the case of "fs:gs:[eax]", you can replace it with
> "fs:[eax]" to get the same output.
In straight line code yes. But what if a first override is hidden deep in a
macro you can't or don't want to modify, but you need to add an override to in
one special case?
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, jbeulich at novell dot com, 2017/11/10
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, jbeulich at novell dot com, 2017/11/10
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, hjl.tools at gmail dot com, 2017/11/10
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, jbeulich at novell dot com, 2017/11/10
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, hjl.tools at gmail dot com, 2017/11/10
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel,
jbeulich at novell dot com <=
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, hjl.tools at gmail dot com, 2017/11/10
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, jbeulich at novell dot com, 2017/11/10
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, hjl.tools at gmail dot com, 2017/11/10
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, ubizjak at gmail dot com, 2017/11/10
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, ubizjak at gmail dot com, 2017/11/10
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, jbeulich at novell dot com, 2017/11/13
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, hjl.tools at gmail dot com, 2017/11/13
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, jbeulich at novell dot com, 2017/11/13
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, hjl.tools at gmail dot com, 2017/11/13
- [Bug gas/21874] x86: Multiple segment registers in the address are not detected with -masm=intel, jbeulich at novell dot com, 2017/11/14