From: oliver <oliver@first.in-berlin.de>
To: oleg@okmij.org
Cc: caml-list@inria.fr, ontologiae@gmail.com
Subject: Re: [Caml-list] Why NOT to compile OCaml via C
Date: Sat, 10 Dec 2011 00:01:08 +0100 [thread overview]
Message-ID: <20111209230108.GC8946@siouxsie> (raw)
In-Reply-To: <20111209065758.94306.qmail@eeoth.pair.com>
On Fri, Dec 09, 2011 at 06:57:58AM -0000, oleg@okmij.org wrote:
>
> Pierre-Alexandre Voye wrote:
>
> > Note that if Ocaml compiler would have a C backend, all these problems or
> > architecture port would disappear...
> > Ocaml would have more than 30 target[1]
> > In my Opinion, trying to generate assembler is a bad idea because modern CPU
> > require a lot of work to generate good assembler.
>
> There are many good reasons to avoid C when compiling functional
> languages, especially strict ones.
>
> One often hears that ``C is a portable assembler''. That has never
> been true. One of the reasons is that every assembler I know has the
> "jmp" instruction, which, without affecting SP, transfers control
> anywhere, out of a procedure or in the middle of a procedure, out of a
> module or into a module. C is built around the stack discipline --
> after all, C is a descendant of Algol 60. (Although C has labels, they
> are limited, even in GCC). Although Algol-60 researchers quickly
> recognized the value of tail recursion, all that knowledge was lost in
> the Dark Ages.
[...]
This somehow is a good example on "OCaml maintenance status..:" thread
and "Some comments on recent discussions" thread...
If this thread comes to a conclusion, the conclusion maybe can be sent to the OCaml core team...
... if it has new insights.
But my guess is, that we end at a point, where OCaml already is,
because I think these kind of dicsussions were already made,
when the design was chosen.
If something new evolves it could be sent to the core team.
But I just doubt, that this will happen here ;)
Ciao,
Oliver
next prev parent reply other threads:[~2011-12-09 23:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 6:57 oleg
2011-12-09 7:52 ` Stéphane Glondu
2011-12-09 9:58 ` Gabriel Scherer
2011-12-09 10:06 ` [Caml-devel] " Jonathan Protzenko
2011-12-09 11:03 ` Mehdi Dogguy
2011-12-09 12:08 ` Benedikt Meurer
2011-12-09 12:37 ` Gabriel Scherer
2011-12-09 14:05 ` Benedikt Meurer
2011-12-09 14:30 ` Török Edwin
2011-12-09 14:51 ` Benedikt Meurer
2011-12-09 23:38 ` oliver
2011-12-09 21:22 ` Richard W.M. Jones
2011-12-10 9:36 ` Benedikt Meurer
2011-12-10 11:34 ` Jon Harrop
2011-12-09 23:01 ` oliver [this message]
2011-12-09 23:18 ` Goswin von Brederlow
2011-12-10 0:20 ` Till Varoquaux
2011-12-10 7:35 ` oleg
2011-12-10 15:40 ` Basile Starynkevitch
2011-12-10 23:56 ` Peter Hawkins
2011-12-11 8:24 ` Basile Starynkevitch
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=20111209230108.GC8946@siouxsie \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
--cc=oleg@okmij.org \
--cc=ontologiae@gmail.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