From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Andreas Schwab <schwab@suse.de>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
arcml <linux-snps-arc@lists.infradead.org>,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: ELF_INITFINI for ARC (was Re: [PATCH] Introduce <elf-initfini.h> and ELF_INITFINI for all architectures)
Date: Wed, 26 Feb 2020 20:02:16 +0000 [thread overview]
Message-ID: <0982c2d8-c8cc-2969-2846-2d1f39fdc4b0@synopsys.com> (raw)
In-Reply-To: <87y2sp174p.fsf@oldenburg2.str.redhat.com>
On 2/26/20 11:27 AM, Florian Weimer wrote:
> I haven't followed the ARC contribution process closely, sorry. Do you
> plan to contribute the port with a GLIBC_2.32 ABI baseline, or do you
> want to support older binaries for an earlier non-upstream port,
> backdating the baseline?
No we don't need to support old binaries: 2.32 will be baseline
> This matters because in the GLIBC_2.32 case, old binaries will not work
> anyway, so we may as well require that they are rebuilt without
> DT_INIT/DT_FINI. In this case, the glibc master defaults should work.
Understood !
> If you want to support old binaries (which use older symbol versions
> such as GLIBC_2.17), it may make sense to keep DT_INIT/DT_FINI support
> as well. To achieve this, you need to add an <elf-initifini.h> header
> file with
>
> /* Enable DT_INIT/DT_FINI support. */
> #define ELF_INITFINI 1
>
> and keep the crti.S and crtn.S files you already have.
Per the review comments on ARC port last year [1], I was advised to remove the ARC
specific crt*.S so those are anyhow gone.
[1] https://sourceware.org/ml/libc-alpha/2019-01/msg00654.html
prev parent reply other threads:[~2020-02-26 20:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 14:23 [PATCH] Introduce <elf-initfini.h> and ELF_INITFINI for all architectures Florian Weimer
2020-02-05 16:50 ` Adhemerval Zanella
2020-02-09 9:02 ` Florian Weimer
2020-02-18 14:13 ` Florian Weimer
2020-02-20 16:37 ` Andreas Schwab
2020-02-20 16:40 ` Florian Weimer
2020-02-20 16:56 ` Andreas Schwab
2020-02-20 17:11 ` Andreas Schwab
2020-02-20 18:48 ` Florian Weimer
2020-02-20 22:48 ` Jim Wilson
2020-02-21 12:41 ` Florian Weimer
2020-02-21 18:34 ` Florian Weimer
2020-02-21 21:11 ` Jim Wilson
2020-02-21 21:20 ` David Abdurachmanov
2020-02-24 9:13 ` Andreas Schwab
2020-02-24 12:31 ` Florian Weimer
2020-02-24 9:12 ` Andreas Schwab
2020-02-24 10:21 ` Florian Weimer
2020-02-26 19:10 ` ELF_INITFINI for ARC (was Re: [PATCH] Introduce <elf-initfini.h> and ELF_INITFINI for all architectures) Vineet Gupta
2020-02-26 19:27 ` Florian Weimer
2020-02-26 20:02 ` Vineet Gupta [this message]
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0982c2d8-c8cc-2969-2846-2d1f39fdc4b0@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=alistair.francis@wdc.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=schwab@suse.de \
/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).