public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Yinyu Cai <caiyinyu@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] LoongArch: Remove support code for old linker in start.S Date: Tue, 29 Aug 2023 04:33:05 +0000 (GMT) [thread overview] Message-ID: <20230829043305.51856385694E@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=aac842d0edbe53a150ab57a4f776cb50294b6388 commit aac842d0edbe53a150ab57a4f776cb50294b6388 Author: Xi Ruoyao <xry111@xry111.site> Date: Sun Aug 27 00:36:50 2023 +0800 LoongArch: Remove support code for old linker in start.S We are requiring Binutils >= 2.41, so la.pcrel always works here. Signed-off-by: Xi Ruoyao <xry111@xry111.site> Diff: --- sysdeps/loongarch/start.S | 19 +++---------------- 1 file changed, 3 insertions(+), 16 deletions(-) diff --git a/sysdeps/loongarch/start.S b/sysdeps/loongarch/start.S index e9d82033b7..bf6bfc9ea4 100644 --- a/sysdeps/loongarch/start.S +++ b/sysdeps/loongarch/start.S @@ -60,20 +60,7 @@ ENTRY (ENTRY_POINT) cfi_undefined (1) or a5, a0, zero /* rtld_fini */ -#if ENABLE_STATIC_PIE -/* For static PIE, the GOT cannot be used in _start because the GOT entries are - offsets instead of real addresses before __libc_start_main. - __libc_start_main and/or main may be not local, so we rely on the linker to - produce PLT entries for them. GNU ld >= 2.40 supports this. */ -# define LA la.pcrel -#else -/* Old GNU ld (< 2.40) cannot handle PC relative address against a non-local - function correctly. We deem these old linkers failing to support static PIE - and load the addresses from GOT. */ -# define LA la.got -#endif - - LA a0, t0, main + la.pcrel a0, t0, main REG_L a1, sp, 0 ADDI a2, sp, SZREG @@ -84,9 +71,9 @@ ENTRY (ENTRY_POINT) move a4, zero /* used to be fini */ or a6, sp, zero /* stack_end */ - LA ra, t0, __libc_start_main + la.pcrel ra, t0, __libc_start_main jirl ra, ra, 0 - LA ra, t0, abort + la.pcrel ra, t0, abort jirl ra, ra, 0 END (ENTRY_POINT)
reply other threads:[~2023-08-29 4:33 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230829043305.51856385694E@sourceware.org \ --to=caiyinyu@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).