From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v4 04/13] LoongArch: ABI Implementation
Date: Mon, 9 May 2022 08:33:10 -0300 [thread overview]
Message-ID: <71082740-47dc-6684-2fe7-44e43c8e8e61@linaro.org> (raw)
In-Reply-To: <20220509082007.nvn37ol7k66l5htv@google.com>
On 09/05/2022 05:20, Fangrui Song via Libc-alpha wrote:
>
>> +/* Set up the loaded object described by L so its stub function
>> + will jump to the on-demand fixup code __dl_runtime_resolve. */
>> +
>> +static inline int __attribute__ ((always_inline))
>> +elf_machine_runtime_setup (struct link_map *l, struct r_scope_elem *scope[],
>> + int lazy, int profile)
>> +{
>> +#ifndef RTLD_BOOTSTRAP
>> + /* If using PLTs, fill in the first two entries of .got.plt. */
>> + if (l->l_info[DT_JMPREL])
>> + {
>> + extern void _dl_runtime_resolve (void)
>> + __attribute__ ((visibility ("hidden")));
>> + ElfW (Addr) *gotplt = (ElfW (Addr) *) D_PTR (l, l_info[DT_PLTGOT]);
>> + /* If a library is prelinked but we have to relocate anyway,
>> + we have to be able to undo the prelinking of .got.plt.
>> + The prelinker saved the address of .plt for us here. */
>
> prelink has been deprecated and will be removed. You can drop complexity
> here and avoid mentioning prelink.
It was removed already.
next prev parent reply other threads:[~2022-05-09 11:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 2:29 [PATCH v4 00/13] GLIBC LoongArch PATCHES caiyinyu
2022-05-09 2:29 ` [PATCH v4 01/13] LoongArch: Update NEWS and README for the LoongArch port caiyinyu
2022-05-09 2:29 ` [PATCH v4 02/13] LoongArch: Add LoongArch entries to config.h.in caiyinyu
2022-05-09 2:30 ` [PATCH v4 03/13] LoongArch: Add relocations and ELF flags to elf.h and scripts/glibcelf.py caiyinyu
2022-05-09 2:30 ` [PATCH v4 04/13] LoongArch: ABI Implementation caiyinyu
2022-05-09 7:56 ` Fangrui Song
2022-05-24 9:49 ` 回复: " caiyinyu
2022-05-24 19:55 ` Fangrui Song
2022-05-09 8:20 ` Fangrui Song
2022-05-09 11:33 ` Adhemerval Zanella [this message]
2022-05-09 12:39 ` Adhemerval Zanella
2022-05-09 12:46 ` Florian Weimer
2022-05-29 13:10 ` Adhemerval Zanella
2022-05-09 2:30 ` [PATCH v4 05/13] LoongArch: Thread-Local Storage Support caiyinyu
2022-05-09 2:30 ` [PATCH v4 06/13] LoongArch: Generic <math.h> and soft-fp Routines caiyinyu
2022-05-09 2:30 ` [PATCH v4 07/13] LoongArch: Atomic and Locking Routines caiyinyu
2022-05-09 2:30 ` [PATCH v4 08/13] LoongArch: Linux Syscall Interface caiyinyu
2022-05-09 2:30 ` [PATCH v4 09/13] LoongArch: Linux ABI caiyinyu
2022-05-09 2:30 ` [PATCH v4 10/13] LoongArch: Add ABI Lists caiyinyu
-- strict thread matches above, loose matches on Subject: below --
2022-05-09 2:25 [PATCH v3 00/13] GLIBC LoongArch PATCHES caiyinyu
2022-05-09 2:26 ` [PATCH v4 04/13] LoongArch: ABI Implementation caiyinyu
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=71082740-47dc-6684-2fe7-44e43c8e8e61@linaro.org \
--to=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).