From: "David Baelde" <david.baelde@gmail.com>
To: "Florian Weimer" <fw@deneb.enyo.de>
Cc: Tom <tom.primozic@gmail.com>, "OCaml Mailing List" <caml-list@inria.fr>
Subject: Re: [Caml-list] Optimizing Array.blit
Date: Fri, 6 Apr 2007 09:00:09 +0200 [thread overview]
Message-ID: <53c655920704060000w2a768362q38848be3cf263031@mail.gmail.com> (raw)
In-Reply-To: <87r6qy5vxn.fsf@mid.deneb.enyo.de>
Hi,
According to Alain (Frisch I guess), in the bug report that I pointed,
Array.blit causes checks for unboxed floats for every check, and also
has to update GC flags. I don't master the second point but he seems
to suggest that it can be optimized.
In the case of non-overlapping unboxed float arrays, I believe a
simple function similar to mine should work. But I'm not very
confident in mine yet.
Cheers.
--
David
next prev parent reply other threads:[~2007-04-06 7:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 22:19 David Baelde
2007-04-05 17:56 ` [Caml-list] " Tom
2007-04-05 21:54 ` Florian Weimer
2007-04-06 7:00 ` David Baelde [this message]
2007-04-10 0:13 ` David Baelde
2007-04-10 1:26 ` [Caml-list] " Jacques Garrigue
2007-04-10 10:08 ` David Baelde
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=53c655920704060000w2a768362q38848be3cf263031@mail.gmail.com \
--to=david.baelde@gmail.com \
--cc=caml-list@inria.fr \
--cc=david.baelde@ens-lyon.org \
--cc=fw@deneb.enyo.de \
--cc=tom.primozic@gmail.com \
/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).