caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Damien Bobillot <damien.bobillot@m4x.org>
To: Jonathan Roewen <jonathan.roewen@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Video/Audio codecs in ocaml
Date: Thu, 17 Nov 2005 10:51:11 +0100	[thread overview]
Message-ID: <DC8BAF13-C8BB-48B9-AFDC-47EBBFA73A9E@m4x.org> (raw)
In-Reply-To: <ad8cfe7e0511170125v24d402f2pfb34ea06a9f2ff58@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

Jonathan Roewen wrote :

>> With OCaml you can't use features like SIMD instructions of CPUs, and
>> will do many bound checking, so it will be slower.
>> I'm a bit sceptical that ocaml may be as good as C for pure signal
>> processing.
>
> Oh okay. Ah well, I'm doing a pure OCaml OS anyways, so we'll just
> have to wait and see.

Ok, I wasn't aware of that. In this case, you effectively have to  
write it in ocaml.

Did you have a url to this OS projet ?

I don't know how much speed you'll lost compared to C code, but if  
you use native ocaml compilation it shouldn't be a big issue (even if  
it's twice as slow as C, it'll run on recent CPUs ;)).

> Can bounds checking be disabled for just one module ?

The -unsafe option is a compiler option, not a linker option, so I  
think it may has a different value for each .ml file.

>> Writing a mpeg2 decoder won't take less than a week !!!
>
> We'll see. It'd be more like rewriting something like libmpeg2 in
> ocaml I think. It'd be a damn good attempt anyways ;-)

So... good luck ;)

-- 
Damien Bobillot


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2375 bytes --]

  reply	other threads:[~2005-11-17  9:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  4:41 Jonathan Roewen
2005-11-17  5:16 ` Jonathan Roewen
2005-11-17  9:17   ` Damien Bobillot
2005-11-17  9:25     ` Jonathan Roewen
2005-11-17  9:51       ` Damien Bobillot [this message]
2005-11-17 18:46         ` David MENTRE
2005-11-17 18:48           ` Jonathan Roewen
2005-11-17 14:39   ` Brian Hurt
2005-11-17 14:56     ` skaller

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=DC8BAF13-C8BB-48B9-AFDC-47EBBFA73A9E@m4x.org \
    --to=damien.bobillot@m4x.org \
    --cc=caml-list@yquem.inria.fr \
    --cc=jonathan.roewen@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).