public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: LIU Hao <lh_mouse@126.com>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc@gcc.gnu.org
Subject: Re: Please, really, make `-masm=intel` the default for x86
Date: Fri, 25 Nov 2022 14:00:29 +0100	[thread overview]
Message-ID: <CAFiYyc2NEAWvF5W8GSB7+1hvpbFdk0QwcMvagU2aJZjtk0jB2w@mail.gmail.com> (raw)
In-Reply-To: <5110537b-524b-1595-128d-1172a09a48be@126.com>

On Fri, Nov 25, 2022 at 1:03 PM LIU Hao via Gcc <gcc@gcc.gnu.org> wrote:
>
> 在 2022/11/25 17:32, Jakub Jelinek 写道:
> > So just use -masm=intel yourself and don't force it on others.
> >
> > Other people are familiar with AT&T syntax rather than Intel syntax,
> > in fact, as history shows, Intel syntax is a second class citizen that often
> > takes years to fix up for new instructions.  The memory size prefixes for
> > certain vector instructions are complete lottery and has been changed by the
> > assembler over time.
> >
> > And more importantly, various valid sources aren't really compilable at all
> > with Intel syntax, see https://gcc.gnu.org/PR53929 and dups for some details.
> >
>
> Well, if that's your decision, fair enough. I can maintain my own distribution.
>
> Patch attached [1]; bootstrapped on {x86_64,1686}-w64-mingw32 without any issues so far.

it would be also possible to at a configure time choice, or one driven
by config.gcc (thus
*mingw* could default to intel syntax if they like).

Richard.

>
> [1]
> https://github.com/lhmouse/MINGW-packages/blob/gcc-13/mingw-w64-gcc/9000-Deprecate-the-nonsense-AT-T-synax.patch
>
>
> --
> Best regards,
> LIU Hao
>

  reply	other threads:[~2022-11-25 13:00 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
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 [this message]
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=CAFiYyc2NEAWvF5W8GSB7+1hvpbFdk0QwcMvagU2aJZjtk0jB2w@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --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).