mu-client-pypy issueshttps://gitlab.anu.edu.au/mu/mu-client-pypy/-/issues2017-11-11T00:35:27+11:00https://gitlab.anu.edu.au/mu/mu-client-pypy/-/issues/19PyPy-JIT meta issue2017-11-11T00:35:27+11:00Zixian CaiPyPy-JIT meta issue* [ ] AOT and JIT should map a lltype to same mutype.
* [ ] High level type information should be accessible during runtime.
* [ ] Efficient way to encode/decode type information in JitCode. #4
* [ ] CCALL a ufuncptr of an expos...* [ ] AOT and JIT should map a lltype to same mutype.
* [ ] High level type information should be accessible during runtime.
* [ ] Efficient way to encode/decode type information in JitCode. #4
* [ ] CCALL a ufuncptr of an exposed Mu function. #15
* [ ] How to model guards, loops and bridges in Mu.Zixian CaiZixian Caihttps://gitlab.anu.edu.au/mu/mu-client-pypy/-/issues/11Tagged References in RPython2017-10-05T22:02:34+11:00John ZhangTagged References in RPython## Problem Description
It seems that RPython does support tagged pointers. Tagged points can be enabled with the `taggedpointers` option in `translationoptions.py`.
It uses instances of `rpython.rlib.objectmodel.UnboxedValue` to represe...## Problem Description
It seems that RPython does support tagged pointers. Tagged points can be enabled with the `taggedpointers` option in `translationoptions.py`.
It uses instances of `rpython.rlib.objectmodel.UnboxedValue` to represent a tagged pointer.
More research is needed to uncover how tagged pointers are translated in the default C back-end, how the GC handles it, and how it can be translated in Mu back-end.