From: Jan Beulich <jbeulich@suse.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] RISC-V: remove indirection from register tables
Date: Mon, 14 Aug 2023 08:31:10 +0200 [thread overview]
Message-ID: <7e5cae34-523f-9305-237a-370278420f63@suse.com> (raw)
In-Reply-To: <cf567f53-6476-4977-9995-a95563ac96f2@irq.a4lg.com>
On 12.08.2023 04:00, Tsukasa OI wrote:
> On 2023/08/11 22:18, Jan Beulich via Binutils wrote:
>> @@ -575,14 +575,16 @@ enum riscv_seg_mstate
>> MAP_INSN, /* Instructions. */
>> };
>>
>> -extern const char * const riscv_gpr_names_numeric[NGPR];
>> -extern const char * const riscv_gpr_names_abi[NGPR];
>> -extern const char * const riscv_fpr_names_numeric[NFPR];
>> -extern const char * const riscv_fpr_names_abi[NFPR];
>> +#define NRC 5 /* Max characters in register names, incl nul. */
>
> I'd prefer (4+1). Otherwise, it looks okay.
I certainly don't mind switching.
> I also would like to hear others about the naming of this constant
> "NRC". It's short and not bad (even if unchanged, it's okay for me)...
> but I feel there's a better one exists (even if it's longer).
I'm certainly also up for naming improvement suggestions, but to be
honest the longer the name would get, the less likely I would be
willing to agree to switch. Of course in the end it's the maintainers
who have the final say.
Jan
next prev parent reply other threads:[~2023-08-14 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 13:18 Jan Beulich
2023-08-12 2:00 ` Tsukasa OI
2023-08-14 6:31 ` Jan Beulich [this message]
2023-08-15 6:14 ` Nelson Chu
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=7e5cae34-523f-9305-237a-370278420f63@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=research_trasio@irq.a4lg.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).