From: Fangrui Song <i@maskray.me>
To: Nick Clifton <nickc@redhat.com>, Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: RFC: Maintaining a per-macro invocation count
Date: Fri, 17 May 2024 10:54:45 -0700 [thread overview]
Message-ID: <DS7PR12MB5765833A8790F15918603DD5CBEE2@DS7PR12MB5765.namprd12.prod.outlook.com> (raw)
In-Reply-To: <6ff9d733-d307-4aa6-a9d8-62bc9a0f0974@redhat.com>
On Wed, May 15, 2024 at 2:45 AM Nick Clifton <nickc@redhat.com> wrote:
>
> Hi Fangrui,
>
> > This feature looks very useful, which resembles
> > https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Special-format-strings
> >
> >> ‘%=’
> >>
> >> Outputs a number that is unique to each instance of the asm statement in
> >> the entire compilation. This option is useful when creating local labels
> >> and referring to them multiple times in a single template that generates
> >> multiple assembler instructions.
>
> Intersting. I had not considered generating assembler tests in C ... :-)
>
> Cheers
> Nick
>
Jan mentioned at https://sourceware.org/pipermail/binutils/2024-May/134087.html
> Just to mention it - I'm intending to extend \+ support to at least .irp
> and .irpc; whether that can also reasonably be done for .rept I haven't
> checked yet.
I filed https://sourceware.org/bugzilla/show_bug.cgi?id=31752 (gas:
Support \+ in .rept/.irp/.irpc directives) to formally track the
feature request
for loop directives.
prev parent reply other threads:[~2024-05-17 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 17:11 Nick Clifton
2024-05-14 1:12 ` Hans-Peter Nilsson
2024-05-15 9:42 ` Nick Clifton
2024-05-15 5:59 ` Fangrui Song
2024-05-15 9:45 ` Nick Clifton
2024-05-17 17:54 ` Fangrui Song [this message]
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=DS7PR12MB5765833A8790F15918603DD5CBEE2@DS7PR12MB5765.namprd12.prod.outlook.com \
--to=i@maskray.me \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=nickc@redhat.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).