public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Potharla, Rupesh" <Rupesh.Potharla@amd.com>
Cc: "George, Jini Susan" <JiniSusan.George@amd.com>,
	"Parasuraman, Hariharan" <Hariharan.Parasuraman@amd.com>,
	"Natarajan, Kavitha" <Kavitha.Natarajan@amd.com>,
	"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH] bfd: Add Support for DW_FORM_strx* and DW_FORM_addrx*.
Date: Mon, 25 Apr 2022 14:56:40 +0200	[thread overview]
Message-ID: <868fc919-c81c-3724-cec0-9d85983439f8@suse.com> (raw)
In-Reply-To: <DM6PR12MB4219C4BB638321CD26370813E7F79@DM6PR12MB4219.namprd12.prod.outlook.com>

On 22.04.2022 08:36, Potharla, Rupesh via Binutils wrote:
> Requesting to review the attached patch. The patch provides support for strx* and addrx* forms to the bfd library.

There's a change to decode_line_info() which looks unrelated. If it's
related, you will want to explain this in the description. If it's
not related, you will want to split this into a separate patch with
its own justification. The same looks to repeat in
find_abstract_instance() and yet more places. 

There's a use of bfd_realloc() where you forgot to check for failure.

I consider it at least risky to open-code the conversion from index
to actual value into various callers of read_attribute(), instead of
keeping it in read_attribute_value(), as was clearly originally
intended.

In read_indexed_string(), besides swapping the parameter order for no
apparent reason, you go from a 64-bit type to "unsigned long". Are
you sure this is going to be sufficient on 32-bit architectures? I'd
rather see read_indexed_address() use bfd_uint64_t as well ...

Furthermore read_indexed_address() has a return type of "int", but
you mean to return addresses there. Quite likely this wants to at
least be bfd_vma, if not bfd_uint64_t.

There are also quite a few indentation and padding issues, which you
will want to take care of.

To aid reviewers, please try to supply patches inline rather than as
attachment.

Jan


  reply	other threads:[~2022-04-25 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22  6:36 Potharla, Rupesh
2022-04-25 12:56 ` Jan Beulich [this message]
2022-05-08 16:28   ` Potharla, Rupesh
2022-05-17 11:38     ` Jan Beulich

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=868fc919-c81c-3724-cec0-9d85983439f8@suse.com \
    --to=jbeulich@suse.com \
    --cc=Hariharan.Parasuraman@amd.com \
    --cc=JiniSusan.George@amd.com \
    --cc=Kavitha.Natarajan@amd.com \
    --cc=Rupesh.Potharla@amd.com \
    --cc=binutils@sourceware.org \
    /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).