From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: LIU Hao <lh_mouse@126.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Please, really, make `-masm=intel` the default for x86
Date: Fri, 25 Nov 2022 09:30:39 +0000 [thread overview]
Message-ID: <CAH6eHdQhPbiuiqtjxbwgWiVvrtTOADfH_caAAqeALVVQTK6wmA@mail.gmail.com> (raw)
In-Reply-To: <5c25f39d-1f28-3ac9-cb2e-adde5034ed6e@126.com>
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?
next prev parent reply other threads:[~2022-11-25 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 6:39 LIU Hao
2022-11-25 7:37 ` Hi-Angel
2022-11-25 7:56 ` LIU Hao
2022-11-25 8:50 ` Marc Glisse
2022-11-25 9:11 ` LIU Hao
2022-11-25 9:30 ` Jonathan Wakely [this message]
2022-11-25 9:56 ` Iain Sandoe
2022-11-25 9:32 ` Jakub Jelinek
2022-11-25 12:01 ` LIU Hao
2022-11-25 13:00 ` Richard Biener
2022-11-25 13:31 ` David Brown
2022-11-25 7:48 Dave Blanchard
2022-11-25 8:03 ` LIU Hao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH6eHdQhPbiuiqtjxbwgWiVvrtTOADfH_caAAqeALVVQTK6wmA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=lh_mouse@126.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).