caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Richard Jones <rich@annexia.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Ocamlopt x86-32 and SSE2
Date: Tue, 12 May 2009 13:40:57 +0100	[thread overview]
Message-ID: <20090512124057.GA598@annexia.org> (raw)
In-Reply-To: <4A09434D.3020102@inria.fr>

On Tue, May 12, 2009 at 11:37:17AM +0200, Xavier Leroy wrote:
> Richard Jones:
> >AMD Geode then ...
> 
> Apparently, recent versions of the Geode support SSE2 as well.
> Low-power people love vector instruction sets, because it lets them do
> common tasks like audio and video decoding more efficiently, ergo with
> less energy.

I was mostly joking about this - don't worry :-)

> Well, either
> that, or rely on the kernel to trap unimplemented SSE2 instructions
> and emulate them in software.  This is theoretically possible but I'm
> pretty sure neither Linux nor Windows implement it.

<aside>
Even VMWare aren't doing this.  However, it's now relatively common to
have the CPU lie about the true capabilities of its instruction set
(by faking the return from CPUID, which in Linux means that
/proc/cpuinfo flags doesn't give the true picture).  This is done so
that guests can be migrated across machines in a cluser which have
different capabilities.  VMWare called this 'EVC clustering'.
</aside>

> To finish: I'm still very interested in hearing from packagers.  Does
> Debian, for example, already have some packages that are SSE2-only?
> Are these packages specially tagged so that the installer will refuse
> to install them on pre-SSE2 hardware?  What's the party line?

>From the Fedora p.o.v., there's no problem.  We'll just deprecate
OCaml on ancient pre-SSE2 hardware (for new distributions - they can
keep using RHEL 5 on older hardware).

Rich.

-- 
Richard Jones
Red Hat


  parent reply	other threads:[~2009-05-12 12:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090511043120.976EBBC67@yquem.inria.fr>
2009-05-11  7:10 ` Pascal Cuoq
2009-05-12  9:37   ` [Caml-list] " Xavier Leroy
2009-05-12 10:04     ` Sylvain Le Gall
2009-05-25  8:23       ` Sylvain Le Gall
2009-05-12 12:40     ` Richard Jones [this message]
2009-05-13 22:30     ` [Caml-list] " Florian Weimer
     [not found] <20090509100004.353ADBC5C@yquem.inria.fr>
2009-05-09 11:38 ` CUOQ Pascal
2009-05-10  1:52   ` [Caml-list] " Goswin von Brederlow
2009-05-10  2:16     ` Seo Sanghyeon
2009-05-10  3:50       ` Jon Harrop
2009-05-11  8:05         ` Dmitry Bely
2009-05-11  9:26           ` Jon Harrop
2009-05-11  8:43             ` Dmitry Bely
2009-05-11 13:47               ` Jon Harrop
2009-05-11  9:12             ` Andrey Riabushenko
2009-05-10  8:56     ` CUOQ Pascal
2009-05-10 14:47       ` [Caml-list] " Richard Jones
2009-05-10 19:25     ` Florian Weimer
2009-04-28 19:36 Ocamlopt code generator question Dmitry Bely
2009-05-05  9:24 ` [Caml-list] " Xavier Leroy
2009-05-05  9:41   ` Dmitry Bely
2009-05-08 10:21     ` [Caml-list] Ocamlopt x86-32 and SSE2 Xavier Leroy
2009-05-10 11:04       ` David MENTRE
2009-05-11  2:43         ` Jon Harrop
2009-05-10 23:12       ` Matteo Frigo
2009-05-11  2:45         ` Jon Harrop
2009-05-11  7:55       ` Dmitry Bely

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=20090512124057.GA598@annexia.org \
    --to=rich@annexia.org \
    --cc=caml-list@yquem.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).