From: "Stefan O'Rear" <sorear2@gmail.com>
To: libffi-discuss@sourceware.org
Subject: Re: RISC-V port
Date: Fri, 09 Sep 2016 03:15:00 -0000 [thread overview]
Message-ID: <CADJ6UvNK+De_TNPrBmuwCsLtsWG=Pg4CTAm_oqLNkda8BymR-Q@mail.gmail.com> (raw)
In-Reply-To: <874m5q5g3e.fsf@tromey.com>
On Thu, Sep 8, 2016 at 12:47 PM, Tom Tromey <tom@tromey.com> wrote:
> Stefan> I am interested in being the responsible party to get this code into a
> Stefan> mergable condition. I am familiar with the RISC-V ISA and calling
> Stefan> convention and with libffi's broad principles of operation, but not
> Stefan> with the details of libffi internals.
>
> Stefan> How shall we proceed?
>
> I think the best thing to do is, first, make sure the port passes the
> test suite; and, second, submit a PR on github. Any necessary review
> can be done there.
Done.
-s
next prev parent reply other threads:[~2016-09-09 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1473363895.17727.ezmlm@sourceware.org>
2016-09-08 19:47 ` Tom Tromey
2016-09-09 3:15 ` Stefan O'Rear [this message]
2016-09-08 9:17 Stefan O'Rear
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='CADJ6UvNK+De_TNPrBmuwCsLtsWG=Pg4CTAm_oqLNkda8BymR-Q@mail.gmail.com' \
--to=sorear2@gmail.com \
--cc=libffi-discuss@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).