From: Alexander Monakov <amonakov@ispras.ru>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/5] Assume only FLAG_ELF_LIBC6 suport
Date: Thu, 7 Dec 2023 16:14:53 +0300 (MSK) [thread overview]
Message-ID: <68a626c2-736a-05e7-17c3-e474dfada728@ispras.ru> (raw)
In-Reply-To: <20220802145905.2789733-3-adhemerval.zanella@linaro.org>
On Tue, 2 Aug 2022, Adhemerval Zanella via Libc-alpha wrote:
> From: "Lucas A. M. Magalhaes" <lamm@linux.ibm.com>
>
> The older libc versions are obsolete for over twenty years now.
> This patch removes the special flags for libc5 and libc4 and assumes
> that all libraries cached are libc6 compatible and use FLAG_ELF_LIBC6.
>
> Checked with a build for all affected architectures.
>
> Co-authored-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
> --- a/elf/readelflib.c
> +++ b/elf/readelflib.c
> @@ -110,16 +108,6 @@ process_elf_file (const char *file_name, const char *lib, int *flag,
> program_interpreter = (char *) (file_contents + segment->p_offset);
> check_ptr (program_interpreter);
>
> - /* Check if this is enough to classify the binary. */
> - for (j = 0; j < sizeof (interpreters) / sizeof (interpreters [0]);
> - ++j)
> - if (strcmp (program_interpreter, interpreters[j].soname) == 0)
> - {
> - *flag = interpreters[j].flag;
> - break;
> - }
> - break;
> -
> case PT_GNU_PROPERTY:
> /* The NT_GNU_PROPERTY_TYPE_0 note must be aligned to 4 bytes
> in 32-bit objects and to 8 bytes in 64-bit objects. Skip
This hunk removes a 'break', resulting in a nonsensical
fall-through from 'case PT_INTERP' to 'case PT_GNU_PROPERTY'.
Alexander
next prev parent reply other threads:[~2023-12-07 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 14:59 [PATCH 0/5] More features cleanups Adhemerval Zanella
2022-08-02 14:59 ` [PATCH 1/5] Remove missing LD_LIBRARY_VERSION usages Adhemerval Zanella
2022-08-02 15:11 ` Andreas Schwab
2022-08-02 14:59 ` [PATCH 2/5] Assume only FLAG_ELF_LIBC6 suport Adhemerval Zanella
2023-12-07 13:14 ` Alexander Monakov [this message]
2023-12-07 14:40 ` Adhemerval Zanella Netto
2022-08-02 14:59 ` [PATCH 3/5] Remove ldd libc4 support Adhemerval Zanella
2022-08-02 23:35 ` H.J. Lu
2022-08-02 14:59 ` [PATCH 4/5] arm: Remove RELA support Adhemerval Zanella
2022-08-03 18:31 ` Adhemerval Zanella Netto
2022-08-03 19:59 ` Phil Blundell
2022-08-02 14:59 ` [PATCH 5/5] i386: " Adhemerval Zanella
2022-08-02 15:13 ` H.J. Lu
2022-08-04 0:45 ` Fangrui Song
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=68a626c2-736a-05e7-17c3-e474dfada728@ispras.ru \
--to=amonakov@ispras.ru \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@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).