From: Nick Clifton <nickc@redhat.com>
To: Fangrui Song <i@maskray.me>
Cc: binutils@sourceware.org
Subject: Re: Commit: readelf: Improve display of RELR relocations
Date: Fri, 19 Apr 2024 11:55:44 +0100 [thread overview]
Message-ID: <d59f4e3d-ca78-48b2-b4a8-589c503e7650@redhat.com> (raw)
In-Reply-To: <DS7PR12MB57659F007C5FA3B3CE38A2ECCB0E2@DS7PR12MB5765.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
Hi Fangrui Song,
> Relocation section '.relr.dyn' at offset 0x1f4 contains 2 entries:
>
> Considering REL/RELA output, users might misinterpret "entries" as
> "relocation entries" instead of referring to RELR words.
> Overall, the number of relocation entries seems more valuable than the
> number of RELR words (users can infer the number from the section
> size, or the new "Index:" column).
A fair point.
>> The patch also checks for malformed RELR entries (such as an entry
>> with a value of just 1).
>
> Trailing 1 can be utilized by linkers to avoid convergence issues
> (https://reviews.llvm.org/D67164):
Interesting. I had not realised that that could happen.
So how about the attached patch ? It changes the start of the RELR
section display so that it looks something like this:
Relocation section '.relr.dyn' at offset 0x1a0 contains 3 entries which relocate 27 locations:
It also removes the warning about an no-op bitmap entry.
The patch is inefficient in that the section data is loaded twice, once
to count the entries and a second time to display them. But this can
always be fixed up later if it proves to be a significant overhead.
In my testing I did not encounter any delays because of the double
load...
Cheers
Nick
[-- Attachment #2: readelf.relr.patch.2 --]
[-- Type: application/x-troff-man, Size: 13871 bytes --]
next prev parent reply other threads:[~2024-04-19 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 15:56 Nick Clifton
2024-04-12 18:44 ` Fangrui Song
[not found] ` <CAN30aBFj+_Yfs8+WrC7aM0ZWQihGoZ8nMk2DHO7Xkxzw6PgqSA@mail.gmail.com>
2024-04-12 22:04 ` Fangrui Song
[not found] ` <DS7PR12MB576532E4BB26A2211E7A75AACB042@DS7PR12MB5765.namprd12.prod.outlook.com>
2024-04-16 12:22 ` Nick Clifton
2024-04-18 2:28 ` Fangrui Song
[not found] ` <DS7PR12MB57659F007C5FA3B3CE38A2ECCB0E2@DS7PR12MB5765.namprd12.prod.outlook.com>
2024-04-19 10:55 ` Nick Clifton [this message]
2024-04-23 19:37 ` Fangrui Song
[not found] ` <MN0PR12MB5761E8D41391C97D0666D300CB112@MN0PR12MB5761.namprd12.prod.outlook.com>
2024-04-24 11:25 ` Nick Clifton
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=d59f4e3d-ca78-48b2-b4a8-589c503e7650@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=i@maskray.me \
/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).