From: Richard Jones <rich@annexia.org>
To: David Allsopp <dra-news@metastack.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] break and continue for OCaml
Date: Thu, 10 Apr 2008 15:41:29 +0100 [thread overview]
Message-ID: <20080410144128.GD4065@annexia.org> (raw)
In-Reply-To: <003e01c89b15$001f9f30$017ca8c0@countertenor>
On Thu, Apr 10, 2008 at 04:12:49PM +0200, David Allsopp wrote:
> Is there therefore any reasonable performance gain over implementing
> break/continue as a camlp4 extension rather than as a compiler patch?
The posted patch turns the break/continue into jump instructions
(well, jump bytecodes), which should be moderately faster than pushing
an exception stack frame / unwinding the stack.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2008-04-10 14:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 1:59 Sanghyeon Seo
2008-04-10 7:09 ` [Caml-list] " Luc Maranget
2008-04-10 7:11 ` Jean-Christophe Filliâtre
2008-04-10 14:12 ` David Allsopp
2008-04-10 14:41 ` Richard Jones [this message]
2008-04-10 13:39 ` Richard Jones
2008-04-10 14:05 ` Martin Jambon
2008-04-10 14:19 ` Richard Jones
2008-04-10 14:24 ` Michael Wohlwend
2008-04-10 14:35 ` Martin Jambon
2008-04-10 14:38 ` Michael Wohlwend
2008-04-10 22:23 ` Florian Weimer
2008-04-10 20:35 ` Eric Cooper
2008-04-11 0:14 ` Micha
2008-04-11 3:44 Andrew I. Schein
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=20080410144128.GD4065@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.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