Contribute a RISC-V 64 JIT backend

--===============8417745561321305822==
Content-Type: multipart/alternative; boundary="000000000000d8d83b060e64f8c4"

--000000000000d8d83b060e64f8c4
Content-Type: text/plain; charset="UTF-8"

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

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

<div dir=3D"ltr"><div>Hi all,</div><div><br></div><div>I would like to cont=
ribute a RISC-V 64 JIT backend for RPython.=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_basic.py and almost all test_ajit.py =
related tests (except test_rvmprof.py)</div><div>* test_zrpy_gc_boehm.py</d=
iv><div><br></div><div>I am still working on test_zrpy_gc.py though (p.s. I=
 can pass this if I disable malloc inlining).</div><div><br></div><div>I ha=
ven&#39;t done a full translation yet.<br></div><div><br></div><div>## Logi=
stic</div><div><br></div><div>I wonder how<span class=3D"gmail-Lm gmail-ng"=
> you</span> would like to review the patches?=C2=A0 I have roughly 73 pend=
ing commits.=C2=A0 Each commit has a specific reason for change and corresp=
onding test cases (if applicable).</div><div><br></div><div>Is it better 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><br></div=
><div>Thank you.</div><div><br></div><div>Regards,</div><div>Logan<br></div=
></div>

--000000000000d8d83b060e64f8c4--

--===============8417745561321305822==
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]

--===============8417745561321305822==--