caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Nicolas barnier <barnier@recherche.enac.fr>
To: "Caml" <caml-list@inria.fr>
Subject: [Caml-list] Functors, inlining and Camlp4
Date: Tue, 9 Oct 2001 17:54:32 +0200	[thread overview]
Message-ID: <0110091754320I.05684@beige> (raw)

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


             reply	other threads:[~2001-10-09 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09 15:54 Nicolas barnier [this message]
2001-10-09 17:10 ` Daniel de Rauglaudre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0110091754320I.05684@beige \
    --to=barnier@recherche.enac.fr \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).