From: Hi-Angel <hiangel999@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 10:37:55 +0300 [thread overview]
Message-ID: <CAHGDjgC7b2fMyO7Jpu5-F28u-Z4Zq+uCY2du8NZqyz6aS4M83A@mail.gmail.com> (raw)
In-Reply-To: <4b31677c-255c-2796-67c4-2d67f0c9fa60@126.com>
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.
next prev parent reply other threads:[~2022-11-25 7:37 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 [this message]
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
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=CAHGDjgC7b2fMyO7Jpu5-F28u-Z4Zq+uCY2du8NZqyz6aS4M83A@mail.gmail.com \
--to=hiangel999@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).