20 full time programmers, but if each of them has 1/40 of the skills of X.
Leroy, LLVM will get only 50% of the caml native compiler performance.
I'm not sure hype is correlated with value as you seem to imply but i might
be wrong.
This was the troll of the day.
On Wed, Dec 1, 2010 at 11:58 PM, J
numerics and parallelism.
>
>
>
> Cheers,
>
> Jon.
>
>
>
> *From:* ivan chollet [mailto:ivan.chol...@gmail.com]
> *Sent:* 30 August 2010 18:10
> *To:* Jon Harrop
> *Cc:* Jeremy Bem; caml-list List
>
> *Subject:* Re: [Caml-list] Llama Light: a simple impl
rmance gains and makes it
> much easier to write a performant garbage collector. You’ll need to
> sacrifice polymorphic recursion though, which you probably already have
> anyway…
>
>
>
> Cheers,
>
> Jon.
>
>
>
> *From:* caml-list-boun...@yquem.inria.fr [mailto:
OK.
This looks nice and I would be pleased if you could put a few pointers or
explanations on your webpage about your typechecker implementation and how
it differs with OCaml typechecker.
I will get some free time this week and to implement yet another runtime and
bytecode compiler from scratch. N
Hi,
Is it just a fork on Caml light or a new implementation and runtime?
Regards
On Sun, Aug 29, 2010 at 3:42 PM, Jeremy Bem wrote:
> Dear caml-list,
>
> I'm pleased to announce Llama Light, an implementation of the core Caml
> language. It features a typechecker that is small enough to rea
+ HLVM, Moscow ML, MLTon, etc.
Not too bad in my opinion.
I checked your HLVM and it looks like a really nice project. I had heard
about it before but to be honest it's hard to find information about its
design. Maybe you should release the design documents publicly. It could be
also an good incen
o the original caml
designers so we have no way to understand their design choices fully.
Having said that, the two tasks are non exclusive so we can definitely start
a project with all these goals in mind.
-[ Mon, Aug 09, 2010 at 04:37:36PM +1000, ivan chollet ]
> The existing ocaml ru
o the original caml
designers so we have no way to understand their design choices fully.
-[ Mon, Aug 09, 2010 at 04:37:36PM +1000, ivan chollet ]
> The existing ocaml runtime is
> amazing but it's definitely not very community friendly and is in my opinion
> a bit hard to understand gi
I have noted that there are now many implementation of OCaml. Namely :
- caml light
- jocaml
- mincaml
- your implementation ?
etc.
which means there is a lot of interest in implementing tools and runtimes
for ML.
I'm just saying this because I was planning to implement another VM for ML
to addres
again
-Original Message-
From: goswin-...@web.de [mailto:goswin-...@web.de]
Sent: dimanche 9 août 2009 18:14
To: ivan chollet
Cc: 'David Allsopp'; caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: ocaml sefault in bytecode: unanswered questions
"ivan chollet" w
Cool, thanks for that, for some reason this wasn't obvious to me reading the
documentation.
-Original Message-
From: Alain Frisch [mailto:al...@frisch.fr]
Sent: dimanche 9 août 2009 15:55
To: ivan chollet
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: ocaml sefau
ra-n...@metastack.com]
Sent: dimanche 9 août 2009 10:39
To: 'ivan chollet'
Subject: RE: [Caml-list] Re: ocaml sefault in bytecode: unanswered questions
Chapter 18.2 of the manual is what you need it explains the value type
used internally for the heap. In hyper-simplistic terms, wh
...@metastack.com]
Sent: samedi 8 août 2009 19:25
To: 'ivan chollet'
Cc: caml-list@yquem.inria.fr
Subject: RE: [Caml-list] Re: ocaml sefault in bytecode: unanswered questions
When you pass a value to a function, you create a pointer to that value in
the OCaml runtime the GC cant collect the
vid Allsopp [mailto:dra-n...@metastack.com]
Sent: samedi 8 août 2009 19:15
To: 'ivan chollet'; 'Edgar Friendly'
Cc: caml-list@yquem.inria.fr
Subject: RE: [Caml-list] ocaml sefault in bytecode: unanswered questions
Apologies if I'm missing something obvious (I had a good lunch)...
Iv
.
My question is: does the GC know that it cannot collect the unreferenced
myref pointers before the end of the List.iter?
Sorry, I just wanted to ask this question to rule it out.
Thanks again.
On 07-08-2009, ivan chollet wrote:
>
> This GDB was configured a
range!
-Original Message-
From: Edgar Friendly [mailto:thelema...@gmail.com]
Sent: samedi 8 août 2009 15:29
To: ivan chollet
Cc: 'Cedric Auger'; caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocaml sefault in bytecode: unanswered questions
ivan chollet wrote:
> You basical
row nice stacktraces. I guess that was at least the original
design goal of the OCaml team but I may be wrong.
Ivan
-Original Message-
From: Cedric Auger [mailto:cedric.au...@lri.fr]
Sent: vendredi 7 août 2009 20:20
To: ivan chollet
Subject: Re: [Caml-list] ocaml sefault in bytecode:
Hello guys,
I would like to ask a question about ocaml error handling. Actually many
questions that I've never dared asking on the official mailing list. I've
had a few problems sparsely with OCaml bytecode programs throwing a core
dump. When analyzing these core dumps, gdb says it's a "Segment
18 matches
Mail list logo
