From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: John Prevost <prevost@maya.com>, caml-list@inria.fr
Subject: Re: Strange hugeness of .o, .cmo, and .cmi files
Date: Wed, 31 Mar 1999 17:59:12 +0200 [thread overview]
Message-ID: <19990331175912.00500@pauillac.inria.fr> (raw)
In-Reply-To: <ya2soami3jt.fsf@zarya.maya.com>; from John Prevost on Wed, Mar 31, 1999 at 01:19:50AM -0500
> [Surprisingly large .cmo / .o files]
It's hard to say what's happening without seeing the source or the
generated assembly code. If that kind of things doesn't scare you,
just compile with ocamlopt -S and look at the resulting .s file.
However, I'll venture a guess:
> Obviously, there are a lot of fields in the record type, and I
> assume that this is where the blowup is happening, but I'm not at
> all sure where.
OCaml 2.01 had a known code size problem with the
{ record with lbl = newval } construct, when "record" belongs to a
type with many labels. This was fixed in OCaml 2.02, however.
Regards,
- Xavier Leroy
next prev parent reply other threads:[~1999-03-31 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-31 6:19 John Prevost
1999-03-31 15:59 ` Xavier Leroy [this message]
1999-03-31 21:36 ` John Prevost
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=19990331175912.00500@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=prevost@maya.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