From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: colanderman@gmail.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: 3.09.3 release candidate 2
Date: Thu, 14 Sep 2006 09:05:35 +0900 (JST) [thread overview]
Message-ID: <20060914.090535.122594570.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <875c7e070609130947j635a2ef2n9406b7c0f252f71c@mail.gmail.com>
From: "Chris King" <colanderman@gmail.com>
> I remember hearing somewhere that by exposing .cmx files, the compiler
> is able to inline across module boundaries, and thus distributing .cmx
> files is desirable. Is this just a myth? It seems redundant since
> the .cmx files are included in the .cmxa anyway.
This is a frequent confusion. The .cmxa does not contain all the
information from the .cmx, in particular not the inlining
information. This is natural if you think of it: when you compile a
module, you have no way to know in which library are its dependencies,
so you can only look for .cmx's, not for .cmxa's. The .cmxa's are only
used at link time.
You can still compile without the .cmx's, but you loose the
optimizations.
Jacques Garrigue
next prev parent reply other threads:[~2006-09-14 0:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 11:21 3.09.3 release candidate 1 Damien Doligez
2006-08-30 12:18 ` [Caml-list] " Olivier Andrieu
2006-08-30 12:45 ` skaller
2006-08-30 13:06 ` Olivier Andrieu
2006-09-02 9:53 ` Jean-Marie Gaillourdet
2006-09-04 11:42 ` Damien Doligez
2006-09-08 14:47 ` 3.09.3 release candidate 2 Damien Doligez
2006-09-13 2:48 ` [Caml-list] " Aleksey Nogin
2006-09-13 13:30 ` Hendrik Tews
2006-09-13 15:05 ` Nicolas Pouillard
2006-09-13 15:32 ` skaller
2006-09-13 15:55 ` Hendrik Tews
2006-09-13 16:17 ` Nicolas Pouillard
2006-09-13 16:47 ` Chris King
2006-09-14 0:05 ` Jacques Garrigue [this message]
2006-09-14 7:48 ` [Caml-list] " Hendrik Tews
2006-09-13 16:35 ` skaller
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=20060914.090535.122594570.garrigue@math.nagoya-u.ac.jp \
--to=garrigue@math.nagoya-u.ac.jp \
--cc=caml-list@inria.fr \
--cc=colanderman@gmail.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 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).