public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: LIU Hao <lh_mouse@126.com>
To: gcc@gcc.gnu.org
Subject: Please, really, make `-masm=intel` the default for x86
Date: Fri, 25 Nov 2022 14:39:41 +0800	[thread overview]
Message-ID: <4b31677c-255c-2796-67c4-2d67f0c9fa60@126.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1083 bytes --]

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 AT&T syntax is an awkward foreign dialect, designed originally for PDP-11 and spoken by bumpkins 
that knew little about x86 or ARM. No official Intel or AMD documentation ever adopts it. The syntax 
is terrible. Consider:

    movl $1, %eax  ; k; moves $1 into EAX
                   ; but in high-level languages we expect '%eax = $1',
                   ; so it goes awkwardly backwards.

If this looks fine to you, please re-consider:

   cmpl $1, %eax
   jg .L1          ; does this mean 'jump if $1 is greater than %eax'
                   ; or something stupidly reversed?

If CMP still looks fine to you, please consider how to write VFMADD231PD in AT&T syntax, really.


I have been tired of such inconsistency. For God's sake, please deprecate it.


-- 
Best regards,
LIU Hao

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

             reply	other threads:[~2022-11-25  6:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25  6:39 LIU Hao [this message]
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
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=4b31677c-255c-2796-67c4-2d67f0c9fa60@126.com \
    --to=lh_mouse@126.com \
    --cc=gcc@gcc.gnu.org \
    /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).