From: Dmitry Bely <dmitry.bely@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] Re: Int32 vs float unboxing
Date: Wed, 24 Aug 2011 12:10:25 +0400 [thread overview]
Message-ID: <CAMT7qiT_i5wdbS9q8cOhBpj-Z15syfZ-hg_P3N7maBD_Mira+w@mail.gmail.com> (raw)
In-Reply-To: <CAMT7qiSc+KHupf2RzwmWV_WRwNt91wTsyJ0gtYE00krqBA8WZQ@mail.gmail.com>
On Mon, Aug 22, 2011 at 11:19 AM, Dmitry Bely <dmitry.bely@gmail.com> wrote:
> In the code below "s" reference is unboxed in sum_float loop, but not
> in sum_in32. Why?
Answering to myself: because there are some specific float-oriented
optimizations that does not affect Int32.t (although I don't see why
they cannot be applied to Int32.t as well). Anyway, I decided that
implementing XTEA cipher in pure OCaml is a bad idea, so I still can
live without efficient Int32 calculations ;-)
- Dmitry Bely
prev parent reply other threads:[~2011-08-24 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 7:19 [Caml-list] " Dmitry Bely
2011-08-22 7:58 ` Alain Frisch
2011-08-22 8:33 ` Dmitry Bely
2011-08-24 8:10 ` Dmitry Bely [this message]
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=CAMT7qiT_i5wdbS9q8cOhBpj-Z15syfZ-hg_P3N7maBD_Mira+w@mail.gmail.com \
--to=dmitry.bely@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).