From: Philippe Wang <Philippe.Wang@lip6.fr>
To: forum@x9c.fr
Cc: Philippe Wang <philippe.wang@lip6.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] "ok with parallel threads" GC (aka ocaml for multicore)
Date: Tue, 14 Apr 2009 12:21:41 +0200 [thread overview]
Message-ID: <CAA74566-A3A9-4F80-90D0-3E555944928E@lip6.fr> (raw)
In-Reply-To: <BB3C091F-3BE9-4883-A7CF-9D672CDDF829@x9c.fr>
On Apr 10, 2009, at 20:36 CEDT, forum@x9c.fr wrote:
> Would it be correct to assume that the current state of the project
> implies that you have patched the OCaml runtime to make it
> fully reentrant ?
Is this following partial answer relevant enough ?
The garbage collector is clearly separated from the rest of the
runtime library: the GC is contained in a libgc.a and our patched
ocamlopt links programs to this GC. The GC variables are known by the
GC only.
> If so, is this code/patch available for download ?
Officially, not yet (and not before April 20th).
We did not expect the debugging part to be so complex and hard, and
taking so long.
The man power dramatically decreased in late September : the 2
Master's students went back to Master's courses, and the 3 supervisors
had to do research in parallel with teaching.
Some major bug fixes were made in February/March, a lot of major bug
fixes were made in April (yes, these last 2 weeks).
You know, bugs hiding other bugs... however we are hopefully getting
close to the fix point: today there is no known bug ! :-)
Unsupported features are - of course - not considered as bugs. For
instance, posix signals are (currently) not supported. And, as
parallel computing *potentially* requires quite a lot more memory,
some programs can easily end up in a blocked state when the heap
becomes full: our GC (currently) uses (parameterized) fixed size pages
and heap.
The next days, we will concentrate on making benchmarks (if you have
some relevant testing programs, they are welcome), and if we don't
discover new bugs then we will focus on (finishing) writing a
documentation and a building script, for the release.
If we release as such now, we will have too much support to do because
of the lack of documentation. So it's not quite a good idea...
When we have the minimal-but-sufficient documentation, we will make
the release :-)
In parallel, we try to make it work with OS X Leopard 64 bit and/or
ocaml 3.11 (currently we only support 3.10.2 - Linux x86_64).
> Anyway, wholehearted respect for undertaking such a complex project.
> Good luck in your bug-chasing tasks !
Thanks.
--
Philippe Wang
Philippe.Wang \at/ lip6.fr
N.B. I hope we will not discover new bugs in our amd64.S, our assembly
guru is enjoying (abroad with no www) his "vacances de pâques"...
next prev parent reply other threads:[~2009-04-14 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 17:04 Philippe Wang
2009-04-10 20:52 ` [Caml-list] " Jon Harrop
2009-04-10 23:20 ` Jerome Benoit
[not found] ` <BB3C091F-3BE9-4883-A7CF-9D672CDDF829@x9c.fr>
2009-04-14 10:21 ` Philippe Wang [this message]
2009-04-14 14:18 ` xclerc
2009-04-16 9:45 ` Philippe Wang
2009-04-17 22:15 ` Philippe Wang
2009-04-17 22:20 ` Joel Reymont
2009-04-17 22:29 ` Philippe Wang
2009-04-17 23:05 ` forum
2009-04-23 16:49 ` 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=CAA74566-A3A9-4F80-90D0-3E555944928E@lip6.fr \
--to=philippe.wang@lip6.fr \
--cc=caml-list@inria.fr \
--cc=forum@x9c.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