From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Cc: Sun Haiyong <youbest@sina.com>
Subject: Re: [PATCH] stack-direction: Add support for loongarch CPU
Date: Sat, 4 Sep 2021 09:41:38 -0700 [thread overview]
Message-ID: <a3d7a109-dbd6-8ec9-f98f-463dec8b0aab@cs.ucla.edu> (raw)
In-Reply-To: <4764447.07ICAnoMbH@omega>
On 9/4/21 6:16 AM, Bruno Haible wrote:
> Do you know a document which explains the ABI of this
> architecture (I mean: register usage, max number of arguments passed in
> registers, stack direction, stack alignment, etc.)?
Here is some documentation, which includes ABI documentation:
https://github.com/loongson/LoongArch-Documentation
I did see a disclaimer
<https://loongson.github.io/LoongArch-Documentation/LoongArch-Vol1-EN.html#_disclaimer>
saying, "This document provides only periodic information, and the
contents contained may be updated at any time without notice, depending
on the actual situation of the product." and a translator's note saying
"Due to the limited knowledge of the translators, there are some
inevitable errors and omissions existing in this document, please feel
free to correct."
next prev parent reply other threads:[~2021-09-04 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 4:51 [PATCH] stack-direction: Add support for loongarch CPU Sun Haiyong
2021-09-04 13:16 ` Bruno Haible
2021-09-04 16:41 ` Paul Eggert [this message]
2021-09-04 18:44 ` Bruno Haible
-- strict thread matches above, loose matches on Subject: below --
2021-09-08 15:25 孙海勇
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3d7a109-dbd6-8ec9-f98f-463dec8b0aab@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=youbest@sina.com \
/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).