Bonjour,

I've recently "functorized" some piece of code containing critical fragments 
(very frequently called and which process data) to broaden its use, and I 
ended up with an horrible loss of 20% up to 50% (avg 30%) of the execution 
times for my benchmark. So after profiling and checking the mailing archive, 
I've figured out that essentially the lack of inlining in functor application 
was guilty. In one of his answer, Xavier suggested to "manually" inline 
critical code, which, I guess, means to withdraw the functors and 
duplicate/specialize the module code. But I'm quite reluctant to mess it up 
this way. I hardly know anything about Camlp4, but I was wondering if it 
would be possible to automate this tedious task by preprocessing the sources 
with this very trendy and (apparently) cool tool - written by who ? ;-) 
Perhaps could it work for a subset of the functor language ?

Any hint from Daniel's fans or even the guru himself ?

Thanks


-- Nicolas

"Jesus saves, but only Buddha makes incremental backups."
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr