Hi Matti,

Thank you for your information.  I will try these this weekend.

Regards,
Logan


On Tue, Jan 16, 2024, 12:52 AM Matti Picus <matti.pi...@gmail.com> wrote:

> On 16/1/24 07:02, Logan Chien wrote:
>
> > Hi,
> >
> > I have good news: the RISC-V backend can pass as many unit tests as
> > the AArch64 backend.  I got vmprof and codemap working this weekend.
> > I also completed a full translation and got a workable pypy executable.
> >
> > I have two questions now:
> >
> > 1. Are there other test suites that I can check for the correctness?
> > 2. How do we measure the performance?  Do we have a command line that
> > can run all benchmarks?
> >
> > Thank you in advance.
> >
> > Regards,
> > Logan
> >
> > p.s. All changes are at: https://github.com/loganchien/pypy/tree/rv64
>
>
> Very cool.
>
> 1: Eventually we would want a buildbot worker [0] using either actual
> hardware or qemu. Using qemu might be too slow to be practical. It could
> be based off the aarch64 docker file [1] as a template. For now, you
> could follow manually the different steps in a pyp-c-jit-<platform>
> buildbot run [2]: click on the stdio link for each step to follow the
> workflow. The "app-level -A", "extra tests", "lib-python" would give an
> indication of how compatible the rpython code is, and the "pypyjit"
> tests would give an indication of how well the JIT code generation
> follows the other platforms. A deeper compliance test would be to run
> the binary in the workflows from the binary-testing repo [6] against
> some common python libraries.
>
>
> 2: Theses [3] are the benchmarks that feed speed.pypy.org. They are run
> by a buildbot worker [4]. The step of interest is 9, where the command
> line is the top line of [5]. This generates a json results file and also
> some textual output. You will want an additional run with cpython for a
> baseline.
>
>
> Matti
>
>
> [0]
>
> https://foss.heptapod.net/pypy/buildbot/-/blob/branch/default/README_BUILDSLAVE?ref_type=heads
>
> [1]
>
> https://foss.heptapod.net/pypy/buildbot/-/blob/branch/default/docker/DockerfileArm64?ref_type=heads
>
> [2]
> https://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/9219
> for example
>
> [3] https://foss.heptapod.net/pypy/benchmarks
>
> [4]
> https://buildbot.pypy.org/builders/jit-benchmark-linux-x86-64/builds/4056
>
> [5]
>
> https://buildbot.pypy.org/builders/jit-benchmark-linux-x86-64/builds/4056/steps/shell_9/logs/stdio
>
> [6] https://github.com/pypy/binary-testing
>
> _______________________________________________
> 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: tzuhsiang.ch...@gmail.com
>
_______________________________________________
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

Reply via email to