public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nelson Chu <nelson@rivosinc.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: lifang_xia@linux.alibaba.com, binutils@sourceware.org
Subject: Re: [PATCH v2] RISC-V: hash with segment id and pcrel_hi address while recording pcrel_hi
Date: Thu, 4 Jul 2024 17:18:27 +0800	[thread overview]
Message-ID: <CAPpQWtDj-5o=WV9KVHY0ahmTr55+cK=B+g03tE_DRi-cSGhSfw@mail.gmail.com> (raw)
In-Reply-To: <33978d23-0afd-4cab-93b0-d9d75f36e70a@suse.com>

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

The const asection * sounds reasonable and good to me, thanks for the
suggestion :-)

Nelson

On Thu, Jul 4, 2024 at 2:46 PM Jan Beulich <jbeulich@suse.com> wrote:

> On 04.07.2024 03:56, lifang_xia@linux.alibaba.com wrote:
> > --- a/gas/config/tc-riscv.c
> > +++ b/gas/config/tc-riscv.c
> > @@ -1784,6 +1784,7 @@ init_opcode_hash (const struct riscv_opcode
> *opcodes,
> >     help us resolve the corresponding low-part relocation later.  */
> >  typedef struct
> >  {
> > +  segT seg;
>
> Just one minor comment here: segT really being asection *, I think it would
> be desirable to use const asection * here instead, to clarify that there's
> no intent of changing the referenced section. Not using the pre-cooked segT
> may not be very nice, but (a) there's precedent (obj-elf.c:match_section())
> and (b) I think const-correctness is more important overall.
>
> In the end it'll be Nelson anyway to approve the change.
>
> Jan
>

  reply	other threads:[~2024-07-04  9:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21  1:24 [PATCH] " lifang_xia
2024-06-25  4:31 ` Nelson Chu
2024-06-25  8:25   ` Jan Beulich
2024-07-02  3:20     ` lifang_xia
2024-07-02  6:25       ` Jan Beulich
2024-07-04  1:56         ` [PATCH v2] " lifang_xia
2024-07-04  6:45           ` Jan Beulich
2024-07-04  9:18             ` Nelson Chu [this message]
2024-07-04 13:49               ` Nelson Chu
2024-07-05  1:09                 ` lifang_xia

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='CAPpQWtDj-5o=WV9KVHY0ahmTr55+cK=B+g03tE_DRi-cSGhSfw@mail.gmail.com' \
    --to=nelson@rivosinc.com \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=lifang_xia@linux.alibaba.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).