From: Matt Wette <matt.wette@gmail.com>
To: guile-devel@gnu.org
Subject: Re: riscv files for lightening
Date: Sat, 30 Jan 2021 07:14:19 -0800 [thread overview]
Message-ID: <0f055bec-72da-1df1-4a69-f13488920ea8@gmail.com> (raw)
In-Reply-To: <a26f66e2-d5be-b532-e14a-0f3ad5f56925@gmail.com>
On 1/29/21 11:13 AM, Matt Wette wrote:
> Andy,
>
> I took a stab at porting RISC-V from lightning to lightening.
> I have no riscv toolset or computer yet so these are untested.
>
> I copied files from sv/lightning for riscv to wingo/lightening. Patch
> attached.
> The changes are:
> 1) copy lightning/jit_riscv{.c,-cpu.c-fpu.c,-sz.c,.h} to lightening
> 2) s/include "jit_riscv/include "riscv/
> 3) s/git_int/int/ and s/git_uint/uint/
> 4) copied the JIT_RA0, etc defines from jit_private.h to riscv.c
> 5) updated lightening.am
> 6) updated lightening.h
>
> Matt
>
I did find github.com/riscv/riscv/riscv-gnu-toolchain.
I'm going to see where that goes wrt testing.
Matt
prev parent reply other threads:[~2021-01-30 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 19:13 riscv files for lightening Matt Wette
2021-01-30 15:14 ` Matt Wette [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0f055bec-72da-1df1-4a69-f13488920ea8@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-devel@gnu.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).