From: William Chesters <williamc@paneris.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml Speed for Block Convolutions
Date: Wed, 6 Jun 2001 20:35:55 +0200 (CEST) [thread overview]
Message-ID: <15134.30731.137189.386800@beertje.william.bogus> (raw)
In-Reply-To: <200106060203.EAA22757@pauillac.inria.fr>
Hugo Herbelin writes:
> Assume more generally that you can modify any local variable as in the
> (standard) following example:
>
> let fact (mutable n) =
> let mutable r = 1 in
> while n > 0 do
> r <- r * n;
> n <- n - 1
> done;
> r
This doesn't actually make life much easier for the compiler. On
32-bit machines [see other thread!], `r' must be a reference (in the
C++ sense) to a heap object---64-bit float, plus header. In general
it is not safe to overwrite the float value in the heap, if it's
possible that other variables have been assigned to it (unless floats
are assigned by value not by reference, but in that case you get heap
allocation at the time of assignment ...). The analysis necessary for
determining that no such aliasing references can exist, and indeed
that the value can simply be kept in a float register/on the FPU
stack, is already there in the compiler and applies perfectly well to
mutable references.
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-06-06 18:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 13:25 David McClain
2001-06-04 19:51 ` William Chesters
2001-06-04 20:05 ` Chris Hecker
2001-06-04 20:15 ` David McClain
2001-06-04 22:34 ` Markus Mottl
2001-06-06 20:13 ` William Chesters
2001-06-06 22:29 ` Chris Hecker
2001-06-07 7:42 ` William Chesters
2001-06-05 7:22 ` Chris Hecker
2001-06-06 6:27 ` David McClain
2001-06-04 22:14 ` Tom _
2001-06-04 22:57 ` Chris Hecker
2001-06-05 2:52 ` Brian Rogoff
2001-06-05 15:02 ` Stefan Monnier
2001-06-05 10:48 ` Tom _
2001-06-06 2:03 ` Hugo Herbelin
2001-06-06 4:04 ` Charles Martin
2001-06-06 18:25 ` William Chesters
2001-06-06 18:35 ` William Chesters [this message]
2001-06-06 18:40 ` Patrick M Doane
2001-06-07 1:50 ` Hugo Herbelin
2001-06-07 18:20 ` Tom _
2001-06-07 23:49 ` [Caml-list] let mutable (was OCaml Speed for Block Convolutions) Jacques Garrigue
2001-06-08 0:20 ` [Caml-list] Currying in Ocaml Mark Wotton
2001-06-08 10:13 ` Anton Moscal
[not found] ` <Pine.LNX.4.21.0106081015000.1167-100000@hons.cs.usyd.edu.a u>
2001-06-08 0:38 ` Chris Hecker
2001-06-08 8:25 ` [Caml-list] let mutable (was OCaml Speed for Block Convolutions) Ohad Rodeh
2001-06-08 15:21 ` Brian Rogoff
2001-06-08 17:30 ` Pierre Weis
2001-06-08 18:36 ` Stefan Monnier
2001-06-08 19:07 ` Pierre Weis
2001-06-08 19:30 ` Michel Quercia
2001-06-11 6:42 ` [Caml-list] should "a.(i)" be a reference? (was "let mutable") Judicaël Courant
2001-06-11 13:42 ` [Caml-list] let mutable (was OCaml Speed for Block Convolutions) Pierre Weis
2001-06-12 3:21 ` Jacques Garrigue
2001-06-12 7:43 ` Pierre Weis
2001-06-12 8:31 ` Jacques Garrigue
2001-06-12 13:15 ` Georges Brun-Cottan
2001-06-12 21:54 ` John Max Skaller
2001-06-15 9:55 ` Michael Sperber [Mr. Preprocessor]
-- strict thread matches above, loose matches on Subject: below --
2001-06-01 18:38 [Caml-list] OCaml Speed for Block Convolutions David McClain
2001-06-01 22:51 ` Tom _
2001-06-02 0:10 ` Stefan Monnier
2001-06-04 10:12 ` Jacques Garrigue
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=15134.30731.137189.386800@beertje.william.bogus \
--to=williamc@paneris.org \
--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