Hi Armin, Thank you for the reply.
> This should just be #defined to do nothing with Boehm, maybe in rpython/translator/c/src/mem.h With this change and a few RISC-V backend fixes (related to self.cpu.vtable_offset), I can build and run a JIT+BoehmGC PyPy. This configuration (JIT+BoehmGC) can pass test_tokenize and test_zipfile64 (from lib_python_tests.py). Thus, my next step will focus on the differences between JIT+BoehmGC and JIT+IncminimarkGC. I think the differences are: 1. call_malloc_nursery_* (fast/slow paths) 2. shadow stack push/pop updates 3. gcmap 4. write barriers (fast/slow paths) 5. realloc_frame Regards, Logan On Sun, Feb 18, 2024 at 11:06 PM Armin Rigo <armin.r...@gmail.com> wrote: > Hi Logan, > > On Mon, 19 Feb 2024 at 05:02, Logan Chien <tzuhsiang.ch...@gmail.com> > wrote: > > 2890 | OP_GC_INCREASE_ROOT_STACK_DEPTH(l_v498959, /* > nothing */); > > Ah, yet another missing macro. This should just be #defined to do > nothing with Boehm, maybe in rpython/translator/c/src/mem.h in the > section "dummy version of these operations, e.g. with Boehm". > > > Just to be sure, is the following command correct? > > > > python2.7 ./pytest.py rpython/jit/backend/test/test_zll_stress_0.py -s -v > > Yes, that's correct. > > > A bientôt, > Armin >
_______________________________________________ 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
