public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: LIU Hao <lh_mouse@126.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Jan Beulich <jbeulich@suse.com>,
	binutils@sourceware.org, GCC Development <gcc@gcc.gnu.org>
Subject: Re: RFC: Formalization of the Intel assembly syntax (PR53929)
Date: Wed, 31 Jan 2024 18:11:31 +0800	[thread overview]
Message-ID: <50c8f7cb-f938-4e5d-a4bd-dfc1617bc264@126.com> (raw)
In-Reply-To: <alpine.BSF.2.20.16.2401292307170.2620@arjuna.pair.com>


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

在 2024-01-30 12:22, Hans-Peter Nilsson 写道:
> It's #APP #NO_APP, not /APP /NO_APP, for x86_64-linux, even for
> -masm=intel.
> 

For x86_64-w64-mingw64, GCC emits `/APP`; but Clang still emits `#APP`, as other targets. 
(https://gcc.godbolt.org/z/oj8vdGb78)


> That said, I guess you're going to modify gas too.  But please
> don't change the #APP/#NO_APP semantics for non-intel targets.

Probably not.. As mentioned earlier, there is too little interest on this. No progress shall be made 
unless there are comments from MASM authors.

I'm keeping GCC patched locally for now. This patch does not look so horrible: 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53929#c26


-- 
Best regards,
LIU Hao


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

  reply	other threads:[~2024-01-31 10:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  5:34 LIU Hao
2024-01-18  9:02 ` Fangrui Song
2024-01-18 12:54 ` Jan Beulich
2024-01-18 16:40   ` LIU Hao
2024-01-19  9:13     ` Jan Beulich
2024-01-20 12:40       ` LIU Hao
2024-01-22  8:39         ` Jan Beulich
2024-01-23  1:27           ` LIU Hao
2024-01-23  8:38             ` Jan Beulich
2024-01-23  9:00               ` LIU Hao
2024-01-23  9:03                 ` Jan Beulich
2024-01-23  9:21                   ` LIU Hao
2024-01-23  9:37                     ` Jan Beulich
2024-01-30  4:22     ` Hans-Peter Nilsson
2024-01-31 10:11       ` LIU Hao [this message]
     [not found] ` <DS7PR12MB5765DBF9500DE323DB4A8E29CB712@DS7PR12MB5765.namprd12.prod.outlook.com>
2024-01-19  1:42   ` LIU Hao
2024-01-19  7:41     ` Jan Beulich
2024-01-19  8:19     ` Fangrui Song
     [not found]     ` <DS7PR12MB5765654642BE3AD4C7F54E05CB702@DS7PR12MB5765.namprd12.prod.outlook.com>
2024-01-20 12:32       ` 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=50c8f7cb-f938-4e5d-a4bd-dfc1617bc264@126.com \
    --to=lh_mouse@126.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=hp@bitrange.com \
    --cc=jbeulich@suse.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).