From: skaller <skaller@users.sourceforge.net>
To: Jacques Carette <carette@mcmaster.ca>
Cc: Damien Doligez <damien.doligez@inria.fr>,
"'caml users'" <caml-list@inria.fr>
Subject: Re: [Caml-list] Single-case union types as strong typedefs
Date: 27 Oct 2004 03:34:00 +1000 [thread overview]
Message-ID: <1098812039.2903.147.camel@pelican.wigram> (raw)
In-Reply-To: <web-70171963@cgpsrv2.cis.mcmaster.ca>
On Wed, 2004-10-27 at 01:05, Jacques Carette wrote:
> I consider a linker to be an integral part of a compiler 'suite'.
> I could not care less when a particular code
> optimization is done. If it *has* to be done by the linker, then so be it.
> I do not understand why link-time
> optimizations seem to have been somehow less research-worthy
> than other parts of the compiler.
Why do we need separate compilation
and linkage in the style of C on modern systems?
Surely, we would like to have fast compilations, but
why can't the compiler treat that as an automatic
optimisation, rather than a user managed one?
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
next prev parent reply other threads:[~2004-10-26 17:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 1:49 Nathaniel Gray
2004-10-23 3:31 ` Jacques Garrigue
2004-10-23 3:39 ` David Brown
2004-10-23 5:00 ` skaller
2004-10-23 21:49 ` Nathaniel Gray
2004-10-23 21:24 ` Nathaniel Gray
2004-10-23 21:33 ` Nathaniel Gray
2004-10-24 3:00 ` John Prevost
2004-10-24 5:18 ` skaller
2004-10-24 22:52 ` Nathaniel Gray
2004-10-25 13:21 ` Damien Doligez
2004-10-25 14:25 ` Jacques Carette
2004-10-26 14:07 ` Damien Doligez
2004-10-26 15:05 ` Jacques Carette
2004-10-26 17:34 ` skaller [this message]
2004-10-26 20:02 ` [Caml-list] Combined compilation and linking Jon Harrop
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=1098812039.2903.147.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=carette@mcmaster.ca \
--cc=damien.doligez@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