public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/ARM/heads/morello)] aarch64: Add dynamic linker name for the purecap ABI Date: Mon, 30 May 2022 09:51:46 +0000 (GMT) [thread overview] Message-ID: <20220530095146.5A35F3838023@sourceware.org> (raw) https://gcc.gnu.org/g:9df3aca6005b4df7e057bce66024b0ebe4c064f8 commit 9df3aca6005b4df7e057bce66024b0ebe4c064f8 Author: Szabolcs Nagy <szabolcs.nagy@arm.com> Date: Fri Apr 8 15:45:32 2022 +0100 aarch64: Add dynamic linker name for the purecap ABI Both glibc and musl dynamic linker names were added. For a given libc the name is unique per supported ABI. Diff: --- gcc/config/aarch64/aarch64-linux.h | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/gcc/config/aarch64/aarch64-linux.h b/gcc/config/aarch64/aarch64-linux.h index e587e2e9ad6..5e84fdb0eed 100644 --- a/gcc/config/aarch64/aarch64-linux.h +++ b/gcc/config/aarch64/aarch64-linux.h @@ -21,10 +21,12 @@ #ifndef GCC_AARCH64_LINUX_H #define GCC_AARCH64_LINUX_H -#define GLIBC_DYNAMIC_LINKER "/lib/ld-linux-aarch64%{mbig-endian:_be}%{mabi=ilp32:_ilp32}.so.1" +#define GLIBC_DYNAMIC_LINKER \ + "/lib/ld-linux-aarch64%{mbig-endian:_be}%{mabi=ilp32:_ilp32}%{mabi=purecap:_purecap}.so.1" #undef MUSL_DYNAMIC_LINKER -#define MUSL_DYNAMIC_LINKER "/lib/ld-musl-aarch64%{mbig-endian:_be}%{mabi=ilp32:_ilp32}.so.1" +#define MUSL_DYNAMIC_LINKER \ + "/lib/ld-musl-aarch64%{mbig-endian:_be}%{mabi=ilp32:_ilp32}%{mabi=purecap:_purecap}.so.1" #undef ASAN_CC1_SPEC #define ASAN_CC1_SPEC "%{%:sanitize(address):-funwind-tables}"
reply other threads:[~2022-05-30 9:51 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=20220530095146.5A35F3838023@sourceware.org \ --to=nsz@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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).