From: skaller <skaller@users.sourceforge.net>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ackermann test
Date: 10 Feb 2005 00:34:36 +1100 [thread overview]
Message-ID: <1107956075.5022.593.camel@pelican.wigram> (raw)
In-Reply-To: <20050209111730.GB449@first.in-berlin.de>
On Wed, 2005-02-09 at 22:17, Oliver Bandel wrote:
> > int ack(int x, int y) {
> > if (x==0) return y+1;
> > if (y==0) return ack(x-1,1);
> > return ack(x-1,ack(x,y-1));
> > }
> >
> > then gcc-3.4.3 generates better code (optimizes tail calls).
> > -fomit-frame-pointer further speeds it up.
>
> Would be nice to have the comlete benchmark again - now with this
> code (or with an added row for this C-Code).
I only have gcc 3.2.2. With -fomit-frame-pointer and -O3 and -static
for the new C:
new C w/o old C new Felix old Felix HACKED Ocamlopt Ocamlb
y=10 0.5 0.8 1.8 2.9 7 10 0.4 12
y=11 7.4 12.5 16 28 55 75 2 50
y=12 64 98 113 180 290 370 9 220
w/o -- new C code without -fomit-frame-pointer
'old Felix' + 2 ints on stack frame
'HACKED' + 4 ints on stack frame
Felix puts at least 2 extra words on the stack,
probably 3, plus possibly g++ is saving the
'this' pointer which is a 4 word overhead
compared to the C code.
--
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
next prev parent reply other threads:[~2005-02-09 13:34 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 ` [Caml-list] " Michael Walter
2005-02-09 4:13 ` skaller
2005-02-09 9:26 ` Marcin 'Qrczak' Kowalczyk
2005-02-09 11:17 ` Oliver Bandel
2005-02-09 13:34 ` skaller [this message]
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=1107956075.5022.593.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@yquem.inria.fr \
--cc=oliver@first.in-berlin.de \
/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).