From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Cc: Sun Haiyong <youbest@sina.com>
Subject: Re: [PATCH] stack-direction: Add support for loongarch CPU
Date: Sat, 04 Sep 2021 20:44:39 +0200 [thread overview]
Message-ID: <4340885.RL5eaSpR8r@omega> (raw)
In-Reply-To: <a3d7a109-dbd6-8ec9-f98f-463dec8b0aab@cs.ucla.edu>
Paul Eggert wrote:
> Here is some documentation, which includes ABI documentation:
>
> https://github.com/loongson/LoongArch-Documentation
Thanks; I already got these documents from
https://loongson.github.io/LoongArch-Documentation/README-EN.html
But all it contains regarding the ABI is 1 page about register usage: $sp = $r3.
I can't port e.g. libsigsegv or libffcall with so little information.
Bruno
next prev parent reply other threads:[~2021-09-04 18:46 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
2021-09-04 18:44 ` Bruno Haible [this message]
-- 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=4340885.RL5eaSpR8r@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--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).