On 8/1/24 10:03, Maciej Fijalkowski wrote:
Hi Logan
Very cool you are interested in that! It's often useful to hang out on
IRC as you can ask questions directly. I have not taken any looks at
all, but can you tell me what kind of setup does one need for testing
it? Are you using real hardware or emulation?
The approach of starting with tests and getting translation done later
is very much what we have done in the past.
Best,
Maciej
On Mon, 8 Jan 2024 at 09:42, Logan Chien <tzuhsiang.ch...@gmail.com> wrote:
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 PM Logan Chien <tzuhsiang.ch...@gmail.com> 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
Exciting, thanks!
I find IRC too temporary: it is hard to search through. This can be both
an advantage and a disadvantage. Maybe since we have moved development
efforts to github we could try out the github discussions platform. I
opened it up at https://github.com/orgs/pypy/discussions. Of course you
are welcome to use IRC if you are comfortable with it.
In addition to Maciej's questions: is there only one compilation target
or would the backend need to know about the different ISA extensions?
As for patch review and merging: we have a history of long-lived
branches in PyPy. Two examples: the windows 64-bit branch was only
merged once it was quite ready, and led to only small breakage of the
main branches. I recently merged the hpy0.9 branch too early, and the
failing tests masked some other py3.9 failures until I got it under
control, so it would have been better to hold off until it was more
completely finished. Something tho think about.
Matti
_______________________________________________
pypy-dev mailing list -- pypy-dev@python.org
To unsubscribe send an email to pypy-dev-le...@python.org
https://mail.python.org/mailman3/lists/pypy-dev.python.org/
Member address: arch...@mail-archive.com
