From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: "Matej Košík" <5764c029b688c1c0d24a2e97cd764f@gmail.com>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] a question about "ocamlopt" and "ocamldep"
Date: Wed, 14 Mar 2012 12:23:07 +0100 [thread overview]
Message-ID: <CAPFanBG24dwykhjUegS-af7qQ+1HAaryxVYmvVkjoqrNhF+A5g@mail.gmail.com> (raw)
In-Reply-To: <4F607390.5040705@gmail.com>
> :-(
I don't understand. Why is it sad to have the *ability* to perform
cross-module implementation-dependent optimizations (at the inevitable
cost of locally damaging separate compilation) *if* you wish?
On Wed, Mar 14, 2012 at 11:31 AM, Matej Košík
<5764c029b688c1c0d24a2e97cd764f@gmail.com> wrote:
> On 03/13/2012 06:34 PM, Matthias Puech wrote:
>> This is consistent with how ocamlc/ocamlopt work: separate compilation
>> is ensured the way you think by bytecode .cmo compilation: to build a
>> module, you only need the *interfaces* of its dependencies, but it is
>> unfortunately not ensured when compiling to native code, because of the
>> global (inter-modules) optimizations performed (inlining AFAIK). Thus,
>> to build a .cmx module, you need to be aware of the actual *code* of its
>> dependencies.
>
> :-(
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2012-03-14 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 10:31 Matej Košík
2012-03-14 11:23 ` Gabriel Scherer [this message]
2012-03-14 12:38 ` Matej Košík
2012-03-14 13:19 ` Virgile Prevosto
2012-03-14 17:12 ` Gabriel Scherer
-- strict thread matches above, loose matches on Subject: below --
2012-03-13 18:19 Matej Košík
2012-03-13 18:34 ` Matthias Puech
2012-03-13 19:26 ` Gabriel Scherer
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=CAPFanBG24dwykhjUegS-af7qQ+1HAaryxVYmvVkjoqrNhF+A5g@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=5764c029b688c1c0d24a2e97cd764f@gmail.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).