From: "Hongbo Zhang (BLOOMBERG/ 731 LEX)" <hzhang295@bloomberg.net>
To: alain.frisch@lexifi.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocamldep, transitive dependencies, build systems, flambda
Date: Tue, 5 Jul 2016 13:06:38 -0000 [thread overview]
Message-ID: <577BB0DE022B05020039036A_0_53469@p057> (raw)
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
Hi Alain,
I found the same problem when we did aggressive cross-module inlining in bucklescript. It makes it too hard to build a correct build system, so currently the inlining will stop at B, it will not propagate to C, what do other people think about this?
From: alain.frisch@lexifi.com At: 07/04/16 12:49:32
To: caml-list@inria.fr
Subject: Re:[Caml-list] ocamldep, transitive dependencies, build systems, flambda
Moreover, flambda makes the problem actually quite a bit worse. Indeed,
B.cmx can now contain symbolic references to A.cmx, and when compiling
C.cmx, the compiler will complain that it cannot find A.cmx (typically
when a function in B is inlined in C and calls a function in A). This
is warning 58. Simply disabling the warning does not work, since an old
version of A.cmx could remain in lib1/pub, leading to mismatched
implementation digests and to unreliable parallel build.
[-- Attachment #2: Type: text/html, Size: 1933 bytes --]
next reply other threads:[~2016-07-05 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 13:06 Hongbo Zhang (BLOOMBERG/ 731 LEX) [this message]
2016-07-05 13:17 ` Gabriel Scherer
-- strict thread matches above, loose matches on Subject: below --
2016-07-04 16:49 Alain Frisch
2016-07-05 9:17 ` Nick Chapman
2016-07-18 14:47 ` Alain Frisch
2016-07-19 9:20 ` Goswin von Brederlow
2016-07-19 9:46 ` Daniel Bünzli
2016-07-05 12:00 ` François Bobot
2016-07-05 13:53 ` Gerd Stolpmann
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=577BB0DE022B05020039036A_0_53469@p057 \
--to=hzhang295@bloomberg.net \
--cc=alain.frisch@lexifi.com \
--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).