[pypy-dev] cpyext performance

[Maciej Fijalkowski]

On Tue, Jul 10, 2012 at 12:45 PM, Amaury Forgeot d'Arc
<amauryfa at gmail.com>wrote:

> 2012/7/10 Eleytherios Stamatogiannakis <estama at gmail.com>:
> > On 10/07/12 01:04, wlavrijsen at lbl.gov wrote:
> >>
> >> provide a prioritized list of what's still missing for you? I'm
> following
> >> a
> >> more or less random walk otherwise, with most work going into the CINT
> >> backend
> >> at the moment.
> >
> >
> > Do jitted callbacks work?
> >
> > My main use case has to do with sqlite UDFs written in python that are
> > called from sqlite's side.
>
> A callback called from C cannot be jitted, unless it has a loop in Python
> code.
> The loop in the sqlite library does not count. The JIT needs a
> complete understanding of all operations in the loop...
>
> --
> Amaury Forgeot d'Arc
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> http://mail.python.org/mailman/listinfo/pypy-dev
>

Amaury - not true, we can JIT functions from the start. However, they would
still accept wrapped arguments. I can think about a simple way to enable
jitting from the start without the need though.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20120710/02bd26a1/attachment.html>