public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: caiyinyu <caiyinyu@loongson.cn>
To: adhemerval.zanella@linaro.org
Cc: libc-alpha@sourceware.org, i.swmail@xen0n.name,
	xry111@xry111.site, caiyinyu <caiyinyu@loongson.cn>
Subject: [PATCH] LoongArch: Fix ABI related macros in elf.h to keep consistent with binutils[1].
Date: Mon, 31 Oct 2022 11:43:34 +0800	[thread overview]
Message-ID: <20221031034334.3027740-1-caiyinyu@loongson.cn> (raw)

[1]:
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=c4a7e6b56218e1d5a858682186b542e2eae01a4a;hp=0d94a8735055432029237612a6eb9165db1ec9dd
[2]:
Reference: https://loongson.github.io/LoongArch-Documentation/LoongArch-ELF-ABI-EN.html#_e_flags_identifies_abi_type_and_version
---
 elf/elf.h | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/elf/elf.h b/elf/elf.h
index 3f08823a30..383eb5fbff 100644
--- a/elf/elf.h
+++ b/elf/elf.h
@@ -4093,8 +4093,10 @@ enum
 #define R_NDS32_TLS_DESC	119
 
 /* LoongArch ELF Flags */
-#define EF_LARCH_ABI    	0x07
-#define EF_LARCH_ABI_LP64D	0x03
+#define EF_LOONGARCH_ABI_SOFT_FLOAT     0x1
+#define EF_LOONGARCH_ABI_SINGLE_FLOAT   0x2
+#define EF_LOONGARCH_ABI_DOUBLE_FLOAT   0x3
+#define EF_LOONGARCH_OBJABI_V1          0x40
 
 /* LoongArch specific dynamic relocations */
 #define R_LARCH_NONE		0
-- 
2.31.1


             reply	other threads:[~2022-10-31  3:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  3:43 caiyinyu [this message]
2022-10-31  6:34 ` Xi Ruoyao
2022-10-31 13:12   ` Carlos O'Donell
2022-11-01  2:00     ` Xi Ruoyao
2022-11-01  2:02     ` caiyinyu
2022-11-01  2:14       ` Xi Ruoyao
2022-11-02  6:13         ` caiyinyu
2022-11-02  6:19           ` WANG Xuerui
2022-11-02 10:41             ` Xi Ruoyao

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=20221031034334.3027740-1-caiyinyu@loongson.cn \
    --to=caiyinyu@loongson.cn \
    --cc=adhemerval.zanella@linaro.org \
    --cc=i.swmail@xen0n.name \
    --cc=libc-alpha@sourceware.org \
    --cc=xry111@xry111.site \
    /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).