From: "Scott J," <jscott@planetinternet.be>
To: "Jacques Garrigue" <garrigue@kurims.kyoto-u.ac.jp>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] Runtime overflow and what to do
Date: Mon, 14 Oct 2002 13:02:46 +0200 [thread overview]
Message-ID: <008d01c27371$3de287f0$0100a8c0@janxp> (raw)
In-Reply-To: <20021014184615Q.garrigue@kurims.kyoto-u.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
Hi,
I am following the discussion. But do not understand this. Is this a
solution to eliminate overhead in integer arithmetic.
Personnally I thought to try to capture the overflow status flag for the
pentium processor on my Windows XP.
Thx
Scott
----- Original Message -----
From: Jacques Garrigue
To: checker@d6.com
Cc: caml-list@inria.fr
Sent: Monday, October 14, 2002 11:46 AM
Subject: Re: [Caml-list] Runtime overflow and what to do
From: Chris Hecker <checker@d6.com>
> > echo "print_int Sys.word_size" > /tmp/caml$$
> > WORDSIZE=`ocaml /tmp/caml$$`
> > rm -f /tmp/caml$$
>
> We clearly need a "-eval" switch to ocaml, like perl's -e/n/p. :)
The above can be reduced to one line, without temporary file.
In fact, I feel more like we would need a "-silent" option, to get rid
of prompts and types (this is already the default with scripts).
echo "print_int Sys.word_size;;" | \
ocaml | grep "^# ." | sed -e "s/# //" -e "s/- :.*//"
A shorter but more specific approach is
echo "Sys.word_size;;" | ocaml | grep "# -" | sed -e "s/.*= //"
Jacques Garrigue
-------------------
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
[-- Attachment #2: Type: text/html, Size: 3300 bytes --]
next prev parent reply other threads:[~2002-10-14 11:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 15:01 Scott J,
2002-10-10 15:07 ` Maxence Guesdon
2002-10-10 15:11 ` Maxence Guesdon
2002-10-10 15:21 ` Luc Maranget
2002-10-10 18:13 ` Sven LUTHER
2002-10-10 18:57 ` Xavier Leroy
2002-10-10 22:17 ` Scott J,
2002-10-11 8:00 ` Sven LUTHER
2002-10-11 10:16 ` Alessandro Baretta
2002-10-12 16:13 ` John Carr
2002-10-12 16:58 ` Sven LUTHER
2002-10-12 17:12 ` John Prevost
2002-10-13 9:31 ` Xavier Leroy
2002-10-13 9:52 ` Sven LUTHER
2002-10-13 9:57 ` Xavier Leroy
2002-10-13 10:15 ` Sven LUTHER
2002-10-13 13:25 ` John Carr
2002-10-13 9:28 ` Xavier Leroy
2002-10-14 0:56 ` Chris Hecker
2002-10-14 9:46 ` Jacques Garrigue
2002-10-14 11:02 ` Scott J, [this message]
2002-10-14 14:05 ` Tim Freeman
2002-10-14 15:32 ` Stefano Zacchiroli
2002-10-14 16:12 ` Alain Frisch
2002-10-14 16:49 ` [Caml-list] new ocaml switches (was Re: Runtime overflow and what to do) Chris Hecker
2002-10-13 9:25 ` [Caml-list] Runtime overflow and what to do Xavier Leroy
2002-10-13 10:04 ` Daniel de Rauglaudre
2002-10-13 10:29 ` Pierre Weis
2002-10-13 10:47 ` Daniel de Rauglaudre
2002-10-13 12:38 ` Pierre Weis
2002-10-13 16:14 ` Xavier Leroy
2002-10-13 17:06 ` Michel Quercia
2002-10-15 19:15 ` Pierre Weis
2002-10-15 19:25 ` Xavier Leroy
2002-10-16 8:24 ` Pierre Weis
2002-10-13 10:19 ` Pierre Weis
2002-10-11 8:02 ` Sven LUTHER
2002-10-11 6:42 ` Florian Hars
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='008d01c27371$3de287f0$0100a8c0@janxp' \
--to=jscott@planetinternet.be \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
/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