From: Nick Clifton <nickc@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] readelf: Warn zero-sized relocation sections
Date: Fri, 17 Apr 2020 16:46:49 +0100 [thread overview]
Message-ID: <f62d352a-eb57-7e4f-c8ba-6780f23cded6@redhat.com> (raw)
In-Reply-To: <CAMe9rOqar+37v+grh2r+5SWu9UxHBfy8=k4-jhnwsEjAk8QdmA@mail.gmail.com>
Hi Guys,
I am of a mind to allow this patch, given that one of readelf's
main functions is to diagnose problems with ELF files. If these
warnings really are a problem for users however then we could
provide an option to filter them out.
That said, the patch as it currently exists causes lots of new
failures in the linker testsuite for various targets. Especially
powerpc64-linux. There may well be others, eg alpha-linux-gnu,
but my regression tester is still running. The failures are from
messages like this:
readelf: Warning: Section '.rela.plt': zero-sized relocation section
and
readelf: Warning: Section '.rela.dyn': zero-sized relocation section
So H.J. if you want to persist with this feature you will need to
either fix the tests or the check in readelf.
Cheers
Nick
next prev parent reply other threads:[~2020-04-17 15:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 12:25 H.J. Lu
2020-04-14 12:42 ` Jan Beulich
2020-04-14 13:03 ` H.J. Lu
2020-04-14 13:25 ` Jan Beulich
2020-04-14 13:30 ` H.J. Lu
2020-04-14 13:38 ` Jan Beulich
2020-04-14 13:54 ` H.J. Lu
2020-04-17 15:46 ` Nick Clifton [this message]
2020-04-17 17:57 ` H.J. Lu
2020-04-18 0:26 ` Alan Modra
2020-04-18 16:51 ` [PATCH] elf: Strip zero-sized dynamic sections H.J. Lu
2020-04-20 9:35 ` Alan Modra
2020-04-20 13:25 ` V2 " H.J. Lu
2020-04-21 10:20 ` Nick Clifton
2020-04-20 5:33 ` [PATCH] readelf: Warn zero-sized relocation sections Jan Beulich
2020-04-20 10:28 ` Nick Clifton
2020-04-20 12:19 ` Jan Beulich
2020-04-20 17:25 ` Hans-Peter Nilsson
2020-04-21 10:01 ` Nick Clifton
2020-04-21 10:31 ` Jan Beulich
2020-04-22 2:51 ` Hans-Peter Nilsson
2020-04-24 14:04 ` Nick Clifton
2020-04-24 16:20 ` Hans-Peter Nilsson
2020-04-29 15:04 ` Nick Clifton
2020-04-24 17:19 ` Fangrui Song
2020-04-26 15:26 ` Nick Clifton
2020-04-26 15:59 ` H.J. Lu
2020-04-24 17:50 ` Jan Beulich
2020-04-27 11:24 ` 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=f62d352a-eb57-7e4f-c8ba-6780f23cded6@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jbeulich@suse.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).