From: Markus Elfring <Markus.Elfring@web.de>
To: "Richard W. M. Jones" <rjones@redhat.com>, cocci@inria.fr
Subject: Re: [cocci] Influence of build configuration parameter “--enable-flambda” on compilation of OCaml source files
Date: Fri, 3 May 2024 15:15:16 +0200 [thread overview]
Message-ID: <bac341fc-e0ad-4e0b-8ea9-69ce8a5ff791@web.de> (raw)
In-Reply-To: <20240503121530.GV7636@redhat.com>
> It turns out this happens because Fedora enables "flambda" in the
> OCaml compiler (ie. ./configure --enable-flambda).
How will the influence of such a build configuration parameter evolve further
for the compilation of OCaml source files?
Can it trigger adjustments for OCaml software packages?
> flambda is "a series of optimisation passes provided by the native
> code compilers as of OCaml 4.03" which "make it easier to write
> idiomatic OCaml code without incurring performance penalties".
Thanks for such background information.
> It's not enabled by default, which probably explains why this problem is
> not seen on Debian.
Will any corresponding program variations become more interesting?
> I will discuss with Fedora if we want to keep this option enabled or
> drop it. It's not a show-stopper that Coccinelle takes a long time
> to compile, just a bit annoying.
Will corresponding software run time characteristics be checked and improved
any more?
> It doesn't seem to affect Coccinelle in any other way
> (eg. making it faster/slower at runtime) as far as I can tell.
Would anybody like to improve such comparisons in more detail?
Regards,
Markus
next prev parent reply other threads:[~2024-05-03 13:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 8:54 [cocci] Very long compile times on parsing_cocci/parser_cocci_menhir.ml Richard W.M. Jones
2024-05-02 9:01 ` Wolfram Sang
2024-05-02 16:16 ` Richard W.M. Jones
2024-05-02 17:40 ` Wolfram Sang
2024-05-02 9:44 ` Julia Lawall
2024-05-02 16:31 ` Richard W.M. Jones
2024-05-02 16:39 ` Julia Lawall
2024-05-02 16:49 ` Richard W.M. Jones
2024-05-02 17:02 ` Julia Lawall
2024-05-03 12:15 ` Richard W.M. Jones
2024-05-03 13:15 ` Markus Elfring [this message]
2024-05-03 15:50 ` Julia Lawall
2024-05-03 16:43 ` Markus Elfring
2024-05-07 9:45 ` Richard W.M. Jones
2024-05-07 9:56 ` Julia Lawall
2024-05-05 5:25 ` [cocci] Using OCaml compiler variants? Markus Elfring
2024-05-02 17:19 ` [cocci] Very long compile times on parsing_cocci/parser_cocci_menhir.ml Richard W.M. Jones
2024-05-02 17:31 ` Richard W.M. Jones
2024-05-02 21:41 ` Julia Lawall
2024-05-03 7:31 ` Richard W.M. Jones
2024-05-03 8:00 ` Markus Elfring
2024-05-03 10:24 ` Richard W.M. Jones
2024-05-03 10:40 ` [cocci] Analysing software build processes Markus Elfring
2024-05-03 10:59 ` Richard W.M. Jones
2024-05-03 11:15 ` Markus Elfring
2024-05-02 10:18 ` [cocci] Checking compilation durations for “parser_cocci_menhir.ml” Markus Elfring
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=bac341fc-e0ad-4e0b-8ea9-69ce8a5ff791@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=rjones@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.