Hi all,
I would like to announce that callouts are working in JIT now, and all patches
were landed! The only thing which is not supported is callouts between a
conditional block and its condition. At the moment this can only be inserted
using auto-callouts, which is probably not the best use
On 2013-02-13 18:44, Zoltán Herczeg wrote:
Naden, could you try the callout feature? I am really curious whether it gives
any performance boost for your application.
Hi, Zoltan!
Thank you very much for great work. But as I wrote earlier my application
hardly uses callouts as well as all of
On 2013-02-13 18:44, Zoltán Herczeg wrote:
I am really curious whether it gives any performance boost for your application.
The performance will be extracted not directly from JIT-realization of callout,
but from getting JIT ON while a non-callout parts of pattern are processed.
--
## List
Hi,
JIT is designed to fall back to interpreted execution if a pattern is not
supported. So you can enable it even if not all patterns will be supported by
it. I hope the majority of your patterns are already covered by now.
Regards,
Zoltan
ND nad...@mail.ru írta:
On 2013-02-13 18:44, Zoltán
Hi Naden,
ok, I will work on this feature. It is not an easy task, so I cannot promise
when it will be done.
Regards,
Zoltan
ND nad...@mail.ru írta:
Hi, Zoltan!
The question is what to do. 1. Is it worth to implement a restricted callout
mechanism (some members are set to an invalid
Hi, Zoltan!
The question is what to do. 1. Is it worth to implement a restricted callout
mechanism (some members are set to an invalid value)? 2. What should we do with
the ovector? 3. And a theoretical question: is JIT worth when we call expensive
C functions?
1. I see ovector and
