From: Florian Weimer <fw@deneb.enyo.de>
To: malc <malc@pulsesoft.com>
Cc: Dmitry Bely <dbely@mail.ru>, caml-list@inria.fr
Subject: Re: [Caml-list] No unused code linking?
Date: Fri, 11 Nov 2005 14:41:58 +0100 [thread overview]
Message-ID: <87u0ej1eu1.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0511091540001.1280@home.oyster.ru> (malc@pulsesoft.com's message of "Wed, 9 Nov 2005 15:44:01 +0300 (MSK)")
>> IMHO, each header item can be placed into the separate DATA section, so
>> it's not the real problem (the frame table is).
>
> No it can not. The moduler header must be contiguous and not rearranged by
> linker. In absence of .cmx (and name -> mangled name table) OCaml uses the
> header to call functions by position. Thus, as it is now, no part of
> header can be eliminated, which in reality means that almost everything,
> from linkers perspective, is reachable and can not be removed by
> --gc-functions.
The module header oculd be generated by the linker, omitting
references to unused functions (filling the place with a null pointer
or something like that).
next prev parent reply other threads:[~2005-11-11 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 11:11 Dmitry Bely
2005-11-09 11:19 ` [Caml-list] " malc
2005-11-09 11:49 ` Dmitry Bely
2005-11-09 12:44 ` malc
2005-11-11 13:41 ` Florian Weimer [this message]
2005-11-11 15:29 ` Dmitry Bely
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=87u0ej1eu1.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=caml-list@inria.fr \
--cc=dbely@mail.ru \
--cc=malc@pulsesoft.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).