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:21:37 +0800 [thread overview]
Message-ID: <7a1fbc8d-e6f6-4dc5-800a-04771069c00e@126.com> (raw)
In-Reply-To: <708903a7-3c5d-4b2e-b280-be88aa72822b@suse.com>
[-- Attachment #1.1: Type: text/plain, Size: 546 bytes --]
在 2024-01-23 17:03, Jan Beulich 写道:
> Hmm, that would suggest to me that the Dwarf code abuses the interface.
> A "name" certainly shouldn't be an expression. And hence the result of
> the example ought to be
>
> .long "LXXYY"-1 # "LXXYY" minus one
So I shouldn't have checked for `*` right?
The calls to `output_addr_const()` are from `dw2_assemble_integer (int size, rtx x)` in
'gcc/dwarf2asm.cc'. Now I need some directives on how to fix this; parsing the symbol seems awkward.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2024-01-23 9:21 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 [this message]
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=7a1fbc8d-e6f6-4dc5-800a-04771069c00e@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).