From: malc <malc@pulsesoft.com>
To: caml-list@inria.fr
Subject: [Caml-list] Is it really a non issue?
Date: Fri, 11 Jan 2002 16:57:13 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.21.0201111647340.1665-100000@home.oyster.ru> (raw)
I noticed that my bug report was silently moved to 'not a bug'
section. Despite report's subject 'Not a bug, but...' i do think its
atleast an issue. Consider this:
file a.ml:
let a = 1
file a.mli:
val a : int \
val a : int |
........... | n times
val a : int |
val a : int /
After compilation/linking we will get huge .cmi and binary with data
section (n-1)*4(on 32bit architectures) bytes bigger that it should have
been. Current ocamlopt.opt is 12 bytes bigger due to redundant declartions
in bytecomp/lambda.mli(is_guarded,patch_guarded) and
utils/clflags.ml(dump_scheduling), not a big deal but still anoying.
--
mailto:malc@pulsesoft.com
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2002-01-11 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 21:57 malc [this message]
2002-01-11 15:42 ` Xavier Leroy
2002-01-11 19:51 ` Luc Maranget
2002-01-12 5:31 ` Jeremy Fincher
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=Pine.LNX.4.21.0201111647340.1665-100000@home.oyster.ru \
--to=malc@pulsesoft.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).