Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Pierre Weis <Pierre.Weis@inria.fr>
To: Jocelyn.Serot@lasmea.univ-bpclermont.fr (Jocelyn Serot)
Cc: caml-list@inria.fr
Subject: Re: native code compiler and exceptions
Date: Fri, 27 Sep 1996 13:41:34 +0200 (MET DST)	[thread overview]
Message-ID: <199609271141.NAA16641@pauillac.inria.fr> (raw)
In-Reply-To: <199609271119.NAA06433@concorde.inria.fr> from "Jocelyn Serot" at Sep 27, 96 01:21:30 pm


Hello,

> 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
[...]
> 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.

Wao! To ``rely heavily on array bounds violation'' is a very ugly style
of programming. I could not imagine why you need to use this style. I
would suggest that you just avoid these violations : this would rend
your program clearer and fully compatible with the optimizing
compiler. Then, you should gain the full benefit of a native code
compilation. Moreover, if your code is really array bound clear, you
could use the unsafe option of the compiler, that remove every array
bound test. (Waiting for an automatic array bound check removing pass
in the optimizing compiler...)

Pierre Weis

INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis







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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-09-27 11:21 Jocelyn Serot
1996-09-27 11:41 ` Pierre Weis [this message]
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=199609271141.NAA16641@pauillac.inria.fr \
    --to=pierre.weis@inria.fr \
    --cc=Jocelyn.Serot@lasmea.univ-bpclermont.fr \
    --cc=caml-list@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