public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: LIU Hao <lh_mouse@126.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org, GCC Development <gcc@gcc.gnu.org>
Subject: Re: RFC: Formalization of the Intel assembly syntax (PR53929)
Date: Tue, 23 Jan 2024 17:00:42 +0800	[thread overview]
Message-ID: <3d65b2cb-c717-4199-a652-58ce02c3d661@126.com> (raw)
In-Reply-To: <c4ec7b69-3af9-4efc-a661-303649d86f37@suse.com>


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

在 2024-01-23 16:38, Jan Beulich 写道:
> Right, but this is very "draft". You can't blindly assume the gas you use
> actually can deal with quotation.

Let's assume that for the time being, but there's something else; see below.


>> .refptr.bx:
>>           .quad   bx
> 
> Sure, this one needs quoting then, too.

The attached patch contains `&& name[0] != '*'` with a reason: In the function `assemble_name_raw` 
in 'gcc/varasm.cc', if `name` starts with a `*`, then its remaining part is output without 
decoration. I have no idea what `*` means; this `.quad bx` thing apparently results from something like

    assemble_name_raw (file, "*bx");

Quoting this would break the i686 DWARF2 code, which may contain an arithmetic expression like

    .long LXXYY-1    # "LXXYY" minus one

If it was quoted like `.long "LXXYY-1"`, it would mean something very different and cause linker errors.


-- 
Best regards,
LIU Hao


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

  reply	other threads:[~2024-01-23  9:01 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 [this message]
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
     [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=3d65b2cb-c717-4199-a652-58ce02c3d661@126.com \
    --to=lh_mouse@126.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --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).