On Fri, 25 Nov 2022 at 09:16, LIU Hao via Gcc <gcc@gcc.gnu.org> wrote: > > 在 2022/11/25 16:50, Marc Glisse 写道: > > On Fri, 25 Nov 2022, LIU Hao via Gcc wrote: > > > >> I am a Windows developer and I have been writing x86 and amd64 assembly > >> for more than ten years. > >> 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. > > > > The doc for -masm=dialect says: > > > > Darwin does not support ‘intel’. > > > > Assuming that's still true, and even with Mac Intel going away, it doesn't > > help. > > > > Did you mean 'Darwin' instead of 'macOS'?
Darwin is the name used in the GNU target triplet. It's an older name than macOS, which was previously called OS X. > The first-class C and C++ compiler for macOS is Clang anyway; even the thing > named 'gcc' is > effectively Clang. And? GCC still works there. As a Windows developer I'm surprised to hear you suggesting that only the default system compiler matters. Should GCC stop supporting Windows?
