From: Xi Ruoyao <xry111@xry111.site>
To: caiyinyu <caiyinyu@loongson.cn>, libc-alpha@sourceware.org
Cc: adhemerval.zanella@linaro.or, joseph_myers@mentor.com, i@xen0n.name
Subject: Re: [PATCH v6 11/13] LoongArch: Build Infastructure
Date: Wed, 13 Jul 2022 11:07:21 +0800 [thread overview]
Message-ID: <ba5ac762ff1617c2842041fa1c81fe4898a08b92.camel@xry111.site> (raw)
In-Reply-To: <20220708065255.2316410-12-caiyinyu@loongson.cn>
On Fri, 2022-07-08 at 14:52 +0800, caiyinyu wrote:
> grlen=`$CC $CFLAGS $CPPFLAGS -E -dM -xc /dev/null | sed -n 's/^#define __loongarch_grlen \(.*\)/\1/p'`
I suggest to use "__loongarch_lp64" for checking ABI grlen. Consider:
"gcc -march=la464 -mabi=ilp32d ..."
Once ILP32 ABIs are available, will __loongarch_grlen be 64 or 32 in
this case, where the hardware has 64-bit registers but the ABI uses them
as 32-bit? Our documentation is not clear about this question and
currently we understand __loongarch_grlen as hardware GR length instead
of the register length used in ABI [1].
[1]:https://github.com/loongson/LoongArch-Documentation/pull/28#discussion_r917364055
OTOH if you think "we should define __loongarch_grlen as the register
length for ABI, irrelevant to the hardware", you need to inform your
colleagues to clarify it in the doc.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-07-13 3:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 6:52 [PATCH v6 00/13] GLIBC LoongArch PATCHES caiyinyu
2022-07-08 6:52 ` [PATCH v6 01/13] LoongArch: Update NEWS and README for the LoongArch port caiyinyu
2022-07-12 11:06 ` Adhemerval Zanella Netto
2022-07-08 6:52 ` [PATCH v6 02/13] LoongArch: Add LoongArch entries to config.h.in caiyinyu
2022-07-12 18:51 ` Adhemerval Zanella Netto
2022-07-08 6:52 ` [PATCH v6 03/13] LoongArch: Add relocations and ELF flags to elf.h and scripts/glibcelf.py caiyinyu
2022-07-12 19:27 ` Adhemerval Zanella Netto
2022-07-08 6:52 ` [PATCH v6 04/13] LoongArch: ABI Implementation caiyinyu
2022-07-12 20:39 ` Adhemerval Zanella Netto
2022-07-15 1:46 ` caiyinyu
2022-07-08 6:52 ` [PATCH v6 05/13] LoongArch: Thread-Local Storage Support caiyinyu
2022-07-13 13:10 ` Adhemerval Zanella Netto
2022-07-08 6:52 ` [PATCH v6 06/13] LoongArch: Generic <math.h> and soft-fp Routines caiyinyu
2022-07-13 13:25 ` Adhemerval Zanella Netto
2022-07-08 6:52 ` [PATCH v6 07/13] LoongArch: Atomic and Locking Routines caiyinyu
2022-07-13 13:53 ` Adhemerval Zanella Netto
2022-07-15 1:46 ` caiyinyu
2022-07-08 6:52 ` [PATCH v6 08/13] LoongArch: Linux Syscall Interface caiyinyu
2022-07-13 16:19 ` Adhemerval Zanella Netto
2023-09-13 11:05 ` caiyinyu
2022-07-08 6:52 ` [PATCH v6 09/13] LoongArch: Linux ABI caiyinyu
2022-07-13 16:35 ` Adhemerval Zanella Netto
2022-07-15 1:48 ` caiyinyu
2022-07-08 6:52 ` [PATCH v6 10/13] LoongArch: Add ABI Lists caiyinyu
2022-07-13 17:12 ` Adhemerval Zanella Netto
2022-07-08 6:52 ` [PATCH v6 11/13] LoongArch: Build Infastructure caiyinyu
2022-07-13 3:07 ` Xi Ruoyao [this message]
2022-07-13 3:43 ` WANG Xuerui
2022-07-13 7:51 ` caiyinyu
2022-07-13 17:48 ` Adhemerval Zanella Netto
2022-07-15 1:49 ` caiyinyu
2022-07-08 6:52 ` [PATCH v6 12/13] LoongArch: Hard Float Support caiyinyu
2022-07-13 19:22 ` Adhemerval Zanella Netto
2022-07-14 13:00 ` caiyinyu
2022-07-08 7:13 ` [PATCH v6 00/13] GLIBC LoongArch PATCHES Xi Ruoyao
2022-07-08 7:15 ` Xi Ruoyao
2022-07-13 19:55 ` Adhemerval Zanella Netto
2022-07-14 11:33 ` Xi Ruoyao
2022-07-14 12:11 ` Adhemerval Zanella Netto
2022-07-18 13:54 ` Carlos O'Donell
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=ba5ac762ff1617c2842041fa1c81fe4898a08b92.camel@xry111.site \
--to=xry111@xry111.site \
--cc=adhemerval.zanella@linaro.or \
--cc=caiyinyu@loongson.cn \
--cc=i@xen0n.name \
--cc=joseph_myers@mentor.com \
--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).