caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Dmitry Bely <dmitry.bely@gmail.com>
To: David Rajchenbach-Teller <David.Teller@ens-lyon.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Why don't use batteries
Date: Mon, 7 Sep 2009 18:42:30 +0400	[thread overview]
Message-ID: <90823c940909070742n56456266m709eabb0e7aeccc8@mail.gmail.com> (raw)
In-Reply-To: <1252136119.8592.39.camel@Blefuscu>

On Sat, Sep 5, 2009 at 11:35 AM, David
Rajchenbach-Teller<David.Teller@ens-lyon.org> wrote:
> I take it to be a complaint against Batteries in particular
> (helloworld.native is several Mb, when linked statically) and agains the
> compiler in particular (in any given program, most of this is dead code
> which the compiler fails to remove).
>
> Xavier Leroy is aware of the issue. Maybe either he or Xavier Clerc will
> be able to look at it someday.

Returning to an old discussion

http://caml.inria.fr/pub/ml-archives/caml-list/2005/11/048f8f60868cf31d27d7fd66e3914023.en.html

I don't think it can be (and will be) done. We should live with these
big executables with considerable amount of dead code.

> Cheers,
>  David
>
> On Fri, 2009-09-04 at 15:00 +0100, Richard Jones wrote:
>> On Fri, Sep 04, 2009 at 02:49:52PM +0200, Julien Signoles wrote:
>> > 3) It makes my executables too big
>> > Yes, even if it seems to be improved in a close future.
>>
>> Is this a complaint against Batteries in particular or OCaml in
>> general?  OCaml binaries in general are rather large, and it appears
>> to be because the runtime / GC is statically linked.  Do you know how
>> much this would improve with dynamic linking of libasmrun.a (which
>> IIRC was a feature added in 3.11)?
>>
>> Rich.

- Dmitry Bely


  reply	other threads:[~2009-09-07 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04 12:49 Julien Signoles
2009-09-04 14:00 ` [Caml-list] " Richard Jones
2009-09-05  7:35   ` David Rajchenbach-Teller
2009-09-07 14:42     ` Dmitry Bely [this message]
2009-09-05  7:33 ` David Rajchenbach-Teller

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=90823c940909070742n56456266m709eabb0e7aeccc8@mail.gmail.com \
    --to=dmitry.bely@gmail.com \
    --cc=David.Teller@ens-lyon.org \
    --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).