caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jocelyn Serot <Jocelyn.Serot@lasmea.univ-bpclermont.fr>
To: caml-list@margaux.inria.fr
Subject: native code compiler and exceptions
Date: Fri, 27 Sep 1996 13:21:30 METDST	[thread overview]
Message-ID: <199609271119.NAA06433@concorde.inria.fr> (raw)


Hello there,

I wanted to ask the ocaml implementors the following question:

Is there a deep, "fundamental",  reason why certain exceptions (in particular
those raised by array accesses out of bound) are not handled in same way
by the bytecode compiler and the native compiler, or is it a temporary
weakness that will be removed in future releases ?..

Here's - in short ;-) - why i am wondering about that:
I've written an image processing module in ocaml. Some functions in this
module (for example, convolutions, ...) relies heavily on bound-violation
exceptions for handling clipping effect at image boundaries. Well, now every-
things works fine under the bytecode compiler. But i'd like to take advantage
of teh native code compiler to boost all that code a bit...

Thanks for any clue

	Jocelyn
--
E-mail: Jocelyn.Serot@lasmea.univ-bpclermont.fr .............................
S-mail: LASMEA - URA 1793 CNRS, Universite Blaise Pascal, 63177 Aubiere cedex
Tel: (33) 73.40.73.30 - Fax: (33) 73.40.72.62 ...............................
.... http://wwwlasmea.univ-bpclermont.fr/Personnel/Jocelyn.Serot/Welcome.html





             reply	other threads:[~1996-09-27 11:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-09-27 11:21 Jocelyn Serot [this message]
1996-09-27 11:41 ` Pierre Weis
1996-09-27 12:46 Jocelyn Serot
1996-09-27 15:58 ` Pierre Weis
1996-09-27 13:04 Harrison R. Ulrich (contractor)
1996-09-27 16:03 ` Christophe Raffalli
     [not found] <199609271524.RAA27638@pauillac.inria.fr>
1996-09-27 16:01 ` Jocelyn Serot

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=199609271119.NAA06433@concorde.inria.fr \
    --to=jocelyn.serot@lasmea.univ-bpclermont.fr \
    --cc=caml-list@margaux.inria.fr \
    /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).