From: Xavier Leroy <xavier.leroy@inria.fr>
To: John Carr <jfc@MIT.EDU>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Catching exceptions into strings
Date: Mon, 17 Jun 2002 14:31:52 +0200 [thread overview]
Message-ID: <20020617143152.A29486@pauillac.inria.fr> (raw)
In-Reply-To: <200206142123.RAA10195@psi-phi.mit.edu>; from jfc@MIT.EDU on Fri, Jun 14, 2002 at 05:23:36PM -0400
> I don't see the problem with translating SIGFPE into an exception.
> The same technique is used for bounds checking. On SPARC/Solaris
> SIGILL becomes an array bounds error.
Correct; same thing for the PowerPC. However, this is implemented
correctly for 5 Unix variants out of 7 supported for these processors
(I haven't figured out how to do it for SPARC/Linux and SPARC/BSD),
and the implementation is further simplified by the assumption that C
code doesn't contain "trap" instructions.
For division by zero, you need to distinguish between SIGFPE generated
inside or outside Caml code, and get the thing working for about 20
different Unix variants. Go ahead.
- Xavier Leroy
-------------------
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:[~2002-06-17 12:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 14:27 Gaurav Chanda
2002-06-10 15:07 ` Xavier Leroy
2002-06-10 21:57 ` Michael Vanier
2002-06-12 8:53 ` Xavier Leroy
2002-06-12 9:36 ` Michael Vanier
2002-06-17 12:48 ` Xavier Leroy
2002-06-17 16:10 ` Ken Rose
2002-06-11 9:23 ` Guillaume Valadon
2002-06-11 13:28 ` David Chase
2002-06-11 15:37 ` Xavier Leroy
2002-06-11 17:44 ` David Chase
2002-06-12 8:33 ` Xavier Leroy
2002-06-11 21:19 ` Michael Vanier
2002-06-14 21:23 ` John Carr
2002-06-17 12:31 ` Xavier Leroy [this message]
2002-06-17 21:08 ` John Carr
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=20020617143152.A29486@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=jfc@MIT.EDU \
/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).