From: Dario Teixeira <darioteixeira@yahoo.com>
To: caml-list@inria.fr, Philippe Wang <philippe.wang@lip6.fr>
Subject: Re: [Caml-list] OC4MC : OCaml for Multicore architectures
Date: Thu, 24 Sep 2009 07:11:24 -0700 (PDT) [thread overview]
Message-ID: <613980.13877.qm@web111508.mail.gq1.yahoo.com> (raw)
In-Reply-To: <D221B09D-9309-4CCF-90E4-CCEDF595BFE2@lip6.fr>
Hi,
Cheers for the work you guys put into this project! And I'd like to join
the crowd that has questions, if I may:
a) If I understand correctly, part of prerequisites for implementing the
new GC was cleaning up the excessive use of imperative constructs in
the compiler's tree. Will the new tree be also more amenable to the
implementation of new language constructs such as GADTs?
b) Could you quantify the performance penalty (if any) of using the new GC
in a single-thread context? And should this penalty be significant, are
there provisions for a compile-time choice of which GC to use?
c) Is there an understanding between you and the folks at INRIA concerning
the eventual merging of this code into the mainline tree?
Thanks a lot for your time!
Best regards,
Dario Teixeira
next prev parent reply other threads:[~2009-09-24 14:11 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 21:30 Philippe Wang
2009-09-23 10:53 ` [Caml-list] " Goswin von Brederlow
2009-09-23 12:21 ` Jon Harrop
2009-09-23 13:00 ` Jon Harrop
2009-09-23 14:26 ` Philippe Wang
2009-09-24 0:21 ` Jon Harrop
2009-09-23 23:15 ` Philippe Wang
2009-09-24 0:05 ` Jon Harrop
2009-09-24 0:01 ` Philippe Wang
2009-09-24 1:47 ` Jon Harrop
2009-09-24 9:49 ` Richard Jones
2009-09-24 10:00 ` rixed
2009-09-24 10:40 ` Florian Hars
2009-09-24 11:45 ` Jon Harrop
2009-09-24 10:00 ` kcheung
2009-09-24 11:52 ` Jon Harrop
2009-09-24 11:55 ` Rakotomandimby Mihamina
2009-09-24 12:11 ` rixed
2009-09-24 15:58 ` Jon Harrop
2009-09-24 12:39 ` Stefano Zacchiroli
2009-09-24 13:09 ` Jon Harrop
2009-09-24 16:49 ` Richard Jones
2009-09-24 16:56 ` Philippe Wang
2009-09-24 17:36 ` Richard Jones
2009-09-24 19:39 ` rixed
2009-09-24 21:09 ` Jon Harrop
2009-09-24 21:26 ` rixed
2009-09-25 4:07 ` Jacques Garrigue
2009-09-25 7:32 ` Hugo Ferreira
2009-09-25 10:17 ` Jon Harrop
2009-09-25 13:04 ` kcheung
2009-09-25 21:39 ` Gerd Stolpmann
2009-09-25 9:33 ` Philippe Wang
2009-09-25 21:39 ` Jon Harrop
2009-09-26 16:55 ` Jon Harrop
2009-09-25 8:08 ` Stéphane Glondu
2009-09-25 15:05 ` Xavier Leroy
2009-09-25 23:26 ` Benjamin Canou
2009-09-26 0:45 ` kcheung
2009-09-26 1:53 ` Jon Harrop
2009-09-26 13:51 ` kcheung
2009-09-26 14:46 ` Jon Harrop
2009-10-10 4:01 ` Jon Harrop
2009-09-24 13:40 ` Rakotomandimby Mihamina
2009-09-24 14:22 ` Philippe Wang
2009-09-24 14:49 ` Stefano Zacchiroli
2009-09-24 13:55 ` Mike Lin
2009-09-24 14:52 ` Stefano Zacchiroli
2009-09-24 15:36 ` Philippe Wang
2009-09-24 15:50 ` Jon Harrop
2009-09-24 12:14 ` Philippe Wang
2009-09-24 13:11 ` Jon Harrop
2009-09-24 14:51 ` Philippe Wang
2009-09-24 14:57 ` Philippe Wang
2009-09-24 14:11 ` Dario Teixeira [this message]
2009-09-24 14:38 ` Philippe Wang
2009-09-24 15:20 ` Dario Teixeira
2009-09-24 23:28 ` Jon Harrop
2009-09-24 23:25 ` Philippe Wang
2009-09-25 14:11 ` Philippe Wang
2009-11-08 18:12 ` Jon Harrop
2009-09-24 18:24 ` David Teller
[not found] <20090924154716.BCD0ABC5A@yquem.inria.fr>
2009-09-24 16:02 ` Pascal Cuoq
2009-09-24 16:30 ` Philippe Wang
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=613980.13877.qm@web111508.mail.gq1.yahoo.com \
--to=darioteixeira@yahoo.com \
--cc=caml-list@inria.fr \
--cc=philippe.wang@lip6.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