Re: Contribute a RISC-V 64 JIT backend

--===============5514774021474166953==
Content-Type: multipart/alternative; boundary="00000000000069addf060e6a5281"

--00000000000069addf060e6a5281
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I forgot to include the link in my previous email.

If you want to have a look on my prototype, you can find it here:
https://github.com/loganchien/pypy/tree/rv64

Thanks.

Regards,
Logan



On Sun, Jan 7, 2024 at 5:18=E2=80=AFPM Logan Chien <[email protected]=
om>
wrote:

> Hi all,
>
> I would like to contribute a RISC-V 64 JIT backend for RPython.  I have
> made some progress at the end of 2023.
>
> ## Status
>
> My prototype can pass the test cases below:
>
> * test_runner.py
> * test_basic.py and almost all test_ajit.py related tests (except
> test_rvmprof.py)
> * test_zrpy_gc_boehm.py
>
> I am still working on test_zrpy_gc.py though (p.s. I can pass this if I
> disable malloc inlining).
>
> I haven't done a full translation yet.
>
> ## Logistic
>
> I wonder how you would like to review the patches?  I have roughly 73
> pending commits.  Each commit has a specific reason for change and
> corresponding test cases (if applicable).
>
> Is it better to just send one GitHub Pull Request containing all of them?
>
> Or, do you prefer one commit per Pull Request?
>
> Thank you.
>
> Regards,
> Logan
>

--00000000000069addf060e6a5281
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>I forgot to include the =
link in my previous email.<br></div><div><br></div><div>If you want to have=
 a look on my prototype, you can find it here:</div><div><a href=3D"https:/=
/github.com/loganchien/pypy/tree/rv64">https://github.com/loganchien/pypy/t=
ree/rv64</a></div><div><br></div><div>Thanks.</div><div><br></div><div>Rega=
rds,</div><div>Logan<br></div><div><br></div><div><br></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Jan 7, =
2024 at 5:18=E2=80=AFPM Logan Chien &lt;<a href=3D"mailto:tzuhsiang.chien@g=
mail.com">[email protected]</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Hi all,</div><div>=
<br></div><div>I would like to contribute a RISC-V 64 JIT backend for RPyth=
on.=C2=A0 I have made some progress at the end of 2023.</div><div><br></div=
><div>## Status<br></div><div><br></div><div>My prototype can pass the test=
 cases below:</div><div><br></div><div>* test_runner.py</div><div>* test_ba=
sic.py and almost all test_ajit.py related tests (except test_rvmprof.py)</=
div><div>* test_zrpy_gc_boehm.py</div><div><br></div><div>I am still workin=
g on test_zrpy_gc.py though (p.s. I can pass this if I disable malloc inlin=
ing).</div><div><br></div><div>I haven&#39;t done a full translation yet.<b=
r></div><div><br></div><div>## Logistic</div><div><br></div><div>I wonder h=
ow<span> you</span> would like to review the patches?=C2=A0 I have roughly =
73 pending commits.=C2=A0 Each commit has a specific reason for change and =
corresponding test cases (if applicable).</div><div><br></div><div>Is it be=
tter to just send one GitHub Pull Request containing all of them?</div><div=
><br></div><div>Or, do you prefer one commit per Pull Request?</div><div><b=
r></div><div>Thank you.</div><div><br></div><div>Regards,</div><div>Logan<b=
r></div></div>
</blockquote></div>

--00000000000069addf060e6a5281--

--===============5514774021474166953==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
pypy-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/pypy-dev.python.org/
Member address: [email protected]

--===============5514774021474166953==--