From: Michael Walter <michael.walter@gmail.com>
To: skaller@users.sourceforge.net
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] ackermann test
Date: Tue, 8 Feb 2005 23:09:44 -0500 [thread overview]
Message-ID: <877e9a170502082009591db0b4@mail.gmail.com> (raw)
In-Reply-To: <1107921472.5022.410.camel@pelican.wigram>
Where can I find the C code you are using?
Michael
On Tue, 08 Feb 2005 20:02:28 -0800 (PST), skaller
<skaller@users.sourceforge.net> wrote:
> Entirely for amusement, current timings for
> ackermanns function, ack(3,y):
>
> Felix Ocaml bytecode Felix/opt C -O3 Ocaml native code
> ---------------------------------------------------------
> y=10 113 12 7 1.8 0.4
> y=11 ? 50 55 16 2
> y=12 ? 220 290 113 9
>
> Times in seconds on 700MHz PIII.
>
> For y=12, my disk light went on occasionally
> (i.e the process was hitting VM), looks like the size of
> stack frames begins to dominate as y increases?
>
> Be interesting to see comparison with ocaml bytecode/JIT.
>
> --
> John Skaller, mailto:skaller@users.sf.net
> voice: 061-2-9660-0850,
> snail: PO BOX 401 Glebe NSW 2037 Australia
> Checkout the Felix programming language http://felix.sf.net
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2005-02-09 4:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 3:57 skaller
2005-02-09 4:09 ` Michael Walter [this message]
2005-02-09 4:13 ` [Caml-list] " skaller
2005-02-09 9:26 ` Marcin 'Qrczak' Kowalczyk
2005-02-09 11:17 ` Oliver Bandel
2005-02-09 13:34 ` skaller
2005-02-09 14:00 ` Marcin 'Qrczak' Kowalczyk
2005-02-09 15:55 ` skaller
2005-02-09 16:51 ` Jon Harrop
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=877e9a170502082009591db0b4@mail.gmail.com \
--to=michael.walter@gmail.com \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).