From: Tom <tom.primozic@gmail.com>
To: david.baelde@ens-lyon.org
Cc: "OCaml Mailing List" <caml-list@inria.fr>
Subject: Re: [Caml-list] Optimizing Array.blit
Date: Thu, 5 Apr 2007 19:56:18 +0200 [thread overview]
Message-ID: <c1490a380704051056u3a82fbd4w45c823e17952f21d@mail.gmail.com> (raw)
In-Reply-To: <53c655920704041519t77930d38y52003888139b9d2c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
>From http://www.cplusplus.com/memcpy:
the arrays pointed by both the *destination* and *source* parameters
should not overlap (for overlapping memory blocks,
memmove<http://www.cplusplus.com/memmove>is a safer approach).
However, Array.blit allows overlapping of the chunks that are to be copied.
So, probably it is slower because it is checking for the overlapping regions
and dealing with them appropriately.
- Tom
[-- Attachment #2: Type: text/html, Size: 543 bytes --]
next prev parent reply other threads:[~2007-04-05 17:56 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 ` Tom [this message]
2007-04-05 21:54 ` [Caml-list] " Florian Weimer
2007-04-06 7:00 ` David Baelde
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=c1490a380704051056u3a82fbd4w45c823e17952f21d@mail.gmail.com \
--to=tom.primozic@gmail.com \
--cc=caml-list@inria.fr \
--cc=david.baelde@ens-lyon.org \
/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).