From: David Brown <caml-list@davidb.org>
To: Brian Hurt <bhurt@spnz.org>
Cc: Ville-Pertti Keinonen <will@exomi.com>,
Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Great Programming Language Shootout Revived
Date: Fri, 18 Jun 2004 10:07:10 -0700 [thread overview]
Message-ID: <20040618170710.GA5672@davidb.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0406181004460.4305-100000@localhost.localdomain>
On Fri, Jun 18, 2004 at 10:38:45AM -0500, Brian Hurt wrote:
> As a side note, there is a reason why C++ is slower than C, even if you're
> compiling the exact same code. C++ functions need to be able to handle
> exceptions and unroll the stack, even if the function itself doesn't throw
> or catch exceptions. Even if unrolling the stack is a no-op, the function
> generally needs to be able to both be handed off from another function's
> stack unrolling, and hand off to another function's stack unrolling.
That depends on how exceptions are implemented. There is a cost to
exceptions that can be paid at different times:
- At each exception catch (try).
- At each exception occurrence (raise).
- At every call.
I've not actually seen the third case implemented. For some test cases,
the actual function code generated by gcc and g++ are identical. g++
contains an extra descriptor to facilitate stack unwinding. It appears
that g++ pays most of the exception cost on raise (which is probably
best for C++ where exceptions are truly, exceptional).
So, aside from cache differences due to the layout of the structures,
the C-type code should execute at the same speed with C++ and C.
Most gnat (Ada) targets also implement these "zero cost" exceptions,
where the raise pays the cost, rather than catch.
Dave
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-06-18 17:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 18:05 Brian Hurt
2004-06-18 1:18 ` Yaron Minsky
2004-06-18 9:37 ` Sebastien Ferre
2004-06-18 15:45 ` Brian Hurt
2004-06-18 21:39 ` Eray Ozkural
2004-06-18 6:09 ` Brandon J. Van Every
2004-06-18 7:56 ` Ville-Pertti Keinonen
2004-06-18 8:59 ` skaller
2004-06-18 9:57 ` Ville-Pertti Keinonen
2004-06-18 10:48 ` Implementing DSLs in OCaml/CamlP4 (was: Re: [Caml-list] Great Programming Language Shootout Revived) Richard Jones
2004-06-18 12:32 ` Walid Taha
2004-06-18 15:38 ` [Caml-list] Great Programming Language Shootout Revived Brian Hurt
2004-06-18 17:07 ` David Brown [this message]
2004-06-19 0:26 ` Nicolas FRANCOIS
2004-06-19 9:04 ` [Caml-list] Benchmark suggestion (Was: Programming Language Shootout) Wolfgang Müller
2004-06-19 10:54 ` Ville-Pertti Keinonen
2004-06-19 19:38 ` [Caml-list] Benchmark suggestion Brandon J. Van Every
2004-06-19 20:08 ` Brian Hurt
2004-06-19 20:16 ` Wolfgang Müller
2004-06-20 11:24 ` [Caml-list] Evangelism Brandon J. Van Every
2004-06-19 11:18 ` [Caml-list] Great Programming Language Shootout Revived Ville-Pertti Keinonen
2004-06-19 11:56 ` Nicolas Janin
2004-06-19 12:51 ` Marcin 'Qrczak' Kowalczyk
2004-06-19 19:46 ` Brandon J. Van Every
2004-06-19 20:19 ` Brian Hurt
2004-06-19 12:09 ` Nicolas Janin
2004-06-19 12:48 ` John Hughes
2004-06-19 18:57 ` Brian Hurt
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=20040618170710.GA5672@davidb.org \
--to=caml-list@davidb.org \
--cc=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=will@exomi.com \
/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