On Sat, Dec 19, 2009 at 20:38, Jeff Shaw shawj...@msu.edu wrote:
My understanding is that since jocaml uses the regular ocaml runtime, it is
also not multicore enabled.
Haskell is a functional language that has good performance that can use
multiple processors, but the learning curve is
On Sun, Dec 20, 2009 at 05:43, Jon Harrop j...@ffconsultancy.com wrote:
As long as you're looking at OCaml's close relatives with multicore support,
F# is your only viable option. Soon, HLVM will provide a cross-platform open
source solution. If you look further you will also find Scala and
Erik Rigtorp wrote:
It's too bad that INRIA is not interested in fixing this bug.
Ask Santa Claus, you'll get it by Friday. Free shipping.
;-)
Martin
___
Caml-list mailing list. Subscription management:
On Sun, Dec 20, 2009 at 7:21 AM, Erik Rigtorp e...@rigtorp.com wrote:
The first step for OCaml would be to be able to run multiple
communicating instances of the runtime bound to one core each in one
process and have them communicate via lock free queues.
We've done some experiments in this
Hi,
It's too bad that INRIA is not interested in fixing this bug. No
matter what people say I consider this a bug. Two cores is standard by
now, I'm used to 8, next year 32 and so on. OCaml will only become
more and more irrelevant. I hate to see that happening.
This is a perennial topic in
Am Sonntag, den 20.12.2009, 08:47 -0500 schrieb Yaron Minsky:
On Sun, Dec 20, 2009 at 7:21 AM, Erik Rigtorp e...@rigtorp.com
wrote:
The first step for OCaml would be to be able to run multiple
communicating instances of the runtime bound to one core each
in one
Am Samstag, den 19.12.2009, 10:30 +0100 schrieb Erik Rigtorp:
Hi!
I've been using Erlang and C++ to build a soft real-time system. As
the project has evolved we've needed to write more and more of the
code in C++ in order to achieve our latency requirements. But C++ is
not as performant as
Excerpts from Jacques Le Normand's message of Sun Dec 20 18:44:57 +0100 2009:
Dear ocaml-list,
the following code does not type check:
type foo = {bar : 'a. 'a - 'a}
let a : int - int = fun x - x
let baz = {bar = Obj.magic a}
with the error
Error: This field value has type 'a - 'a
On Sunday 20 December 2009 14:27:00 Dario Teixeira wrote:
Hi,
It's too bad that INRIA is not interested in fixing this bug. No
matter what people say I consider this a bug. Two cores is standard by
now, I'm used to 8, next year 32 and so on. OCaml will only become
more and more
Am Mittwoch, den 16.12.2009, 17:00 +0100 schrieb Alain Frisch:
On 16/12/2009 16:48, Andre Tampubolon wrote:
I'm trying to build OCaml 3.11.1 using Cygwin.
It's still unsuccessful.
$ make -f Makefile.nt world
cd byterun ; make -f Makefile.nt all
make[1]: Entering directory
The following web page describes a commercial machine sold by Azul Systems
that has up to 16 54-core CPUs (=864 cores) and 768 GB of memory in a flat
SMP configuration:
http://www.azulsystems.com/products/compute_appliance.htm
As you can see, a GC with shared memory can already scale
On Monday 21 December 2009 01:08:14 Gerd Stolpmann wrote:
The following web page describes a commercial machine sold by Azul
Systems that has up to 16 54-core CPUs (=864 cores) and 768 GB of memory
in a flat SMP configuration:
http://www.azulsystems.com/products/compute_appliance.htm
I find the ponderings on the popularity of OCaml to be of limited utility
--- those who pick OCaml based on its popularity are making a terrible
mistake. OCaml was a deeply unpopular language in 2005 and remains so
today, the variations notwithstanding. There are other good reasons to use
the
On Sun, Dec 20, 2009 at 23:30, Jon Harrop j...@ffconsultancy.com wrote:
Traffic here:
2007: 5814
2008: 4051
2009: 3071
That's because I don't have much time to post here nowaydays. I'm
sure if Jon followed my example, we would have a parallel GC for OCaml
by the end of the year.
Regards,
14 matches
Mail list logo
