From: Anthony Green <green@moxielogic.com>
To: 潘学峰 <panxuefeng@loongson.cn>
Cc: libffi-discuss <libffi-discuss@sourceware.org>
Subject: Re: Add a new Architecture to libffi upstream
Date: Sat, 22 Jan 2022 16:54:26 -0500 [thread overview]
Message-ID: <CACxje5-T29K2rPmDnHC=X85qxBnQHdHg=5xfBsBx=Ws19FEPjA@mail.gmail.com> (raw)
In-Reply-To: <2b92dcc1.9d56.17e4d7bbe4e.Coremail.panxuefeng@loongson.cn>
Hello,
There are no specific rules, but off of the top of my head I would say:
- align to existing coding styles and licenses
- implement closure support
- add testing support for the platform (we don't need much -- even a
gdb-based simulator would work -- look at the moxie port for example)
- update the README file
- submit the patches through github PRs
Thanks,
AG
On Wed, Jan 12, 2022 at 3:51 AM 潘学峰 <panxuefeng@loongson.cn> wrote:
>
> Hi all:
>
>
>
>
> Loongarch is a new RISC ISA. I want to add Loongarch code to libffi upstream. I am a newbie in this community, I am not clear about the libffi community code submission rules. Can someone introduce the libffi community code submission rules?
>
>
>
>
> Thanks
prev parent reply other threads:[~2022-01-22 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 8:51 潘学峰
2022-01-22 21:54 ` Anthony Green [this message]
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='CACxje5-T29K2rPmDnHC=X85qxBnQHdHg=5xfBsBx=Ws19FEPjA@mail.gmail.com' \
--to=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
--cc=panxuefeng@loongson.cn \
/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).