On Fri, 25 Nov 2022 at 09:40, LIU Hao via Gcc <gcc@gcc.gnu.org> wrote: > One annoying thing about GCC is that, for x86 if I need to write I piece of > inline assembly then I > have to do it twice: one in AT&T syntax and one in Intel syntax.
Why? A default is merely a default. I don't really see why changing that should help you specifically. A decision "which assembly syntax to use" is one that makes a project like ones you're contributing to, not GCC. If they decided to use AT&T syntax, they won't switch to Intel just because a compiler toolchain has changed their default. If you care specifically about the projects you are contributing to, then those are the ones whom you need to convince to switch to "intel" assembly syntax, not the GCC developers. Because as I said, changing a default in GCC will hardly make any change to those other projects.
