[pypy-dev] cpyext performance

wlavrijsen at lbl.gov wlavrijsen at lbl.gov
Tue Jul 10 20:10:46 CEST 2012

Hi Stefan,

> There's no reason it would require wrapped arguments.

that completely depends on how it is generated, of course, and in the context
of calls within Python (pypy-c), it makes sense to have the entry point of
the function expect wrapped arguments, and have the exit point re-wrap.

> The input types are
> known from the static low-level function type, so the JIT compiler can just
> work with them and adapt the function that is being called.

Yes, except that the above only follows after this:

> These things are trickier in a non-JIT environment, but we are currently
> working on a general framework to support low-level calls through the
> CPython ecosystem (I mentioned that before).

I.e., there should first be a good method of delivering the low-level info.
Right now, that delivery method is the act of unwrapping itself (that is,
the wrapped types carry the low-level info).

Best regards,
WLavrijsen at lbl.gov    --    +1 (510) 486 6411    --    www.lavrijsen.net

More information about the pypy-dev mailing list