caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mike Hogan <MikeHogan62@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] OCalm on Sony PS3 (was Re: More registers in modern day	CPUs)
Date: Sun, 2 Dec 2007 08:22:24 -0800 (PST)	[thread overview]
Message-ID: <14116972.post@talk.nabble.com> (raw)
In-Reply-To: <47528593.9060106@inria.fr>



Xavier Leroy wrote:
> 
> I confirm that OCaml compiles correctly on the PS/3 with YDL.  The
> native-code compiler works fine (in 32-bit mode) provided it's
> configured with  -host powerpc-unknown-linux.  (Autodetection reports
> powerpc64-unknown-linux, even though the default compilation mode on
> this distro is 32-bit; I'll hack the configure script to work around
> this issue.)
> 
Nice -- I'll try the "host powerpc-unknown-linux" option.


Xavier Leroy wrote:
> 
> A more general but extremely difficult approach is two-level
> programming, where the Caml program, running on the PPC core,
> generates programs in a simple data-parallel language which is then
> compiled on the fly to SPU code.  
> 
This is exactly what I would like to do.  There is a Python Extension for
the PS3 SPU's called "CorePy" that can be used to more-or-less directly
generate assembly instructions for the PPC, its associated AltiVec and the
SPUs.  In essence, CorePy makes a class for each particular processor on
your system and this class has processor-specific instructions as methods. 
The extensions take care of the details for loading the code, binding
between the Python interpreter and the assembler that was generated on the
fly etc.


Xavier Leroy wrote:
> 
> Such an approach could also target
> graphics coprocessors (the "GPGPU" approach).  But I have no idea what
> such an intermediate language would look like.
> 
This would actually push the system's abilities up by an order of magnitude
in some cases, but unfortunately the "Other OS" hypervisor on the PS3 bars
access to the GPU.  It's a shame, since the PS3 GPU is supposed to be one of
NVIDIA's hottest chips.
-- 
View this message in context: http://www.nabble.com/More-registers-in-modern-day-CPUs-tf4389938.html#a14116972
Sent from the Caml Discuss2 mailing list archive at Nabble.com.


  reply	other threads:[~2007-12-02 16:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06  6:20 More registers in modern day CPUs Tom
2007-09-06  7:17 ` [Caml-list] " skaller
2007-09-06  9:07 ` Richard Jones
2007-09-06 14:55 ` Chris King
2007-09-06 15:17   ` Brian Hurt
2007-09-06 15:54     ` Harrison, John R
2007-09-06 17:10       ` David MENTRE
2007-09-06 18:27         ` Harrison, John R
2007-09-06 18:28         ` Christophe Raffalli
2007-09-06 18:48           ` Brian Hurt
2007-09-06 18:48           ` Pal-Kristian Engstad
2007-11-20 15:32             ` [Caml-list] OCalm on Sony PS3 (was Re: More registers in modern day CPUs) Mike Hogan
2007-11-21 17:20               ` Richard Jones
2007-11-21 19:05                 ` [Caml-list] OCaml " Mike Hogan
2007-11-23  6:44                 ` Mike Hogan
2007-12-02 10:14               ` [Caml-list] OCalm " Xavier Leroy
2007-12-02 16:22                 ` Mike Hogan [this message]
2007-12-02 22:19                   ` Konrad Meyer
2007-12-03  0:09                     ` [Caml-list] OCaml " Mike Hogan
2007-12-03 20:16                       ` minithread (was OCaml on Sony PS3) Christophe Raffalli
2007-12-04 14:25                         ` [Caml-list] " David MENTRE
2007-12-04 14:37                         ` Basile STARYNKEVITCH
2007-12-04 16:25                           ` Mattias Engdegård
2007-12-04 17:33                         ` Gerd Stolpmann
2007-12-04 18:00                         ` Mike Hogan
2007-12-04  2:29                 ` [Caml-list] OCalm on Sony PS3 (was Re: More registers in modern day CPUs) Gordon Henriksen
2007-09-06 20:48   ` [Caml-list] More registers in modern day CPUs Richard Jones
     [not found]   ` <20070906204524.GB10798@furbychan.cocan.org>
2007-09-06 20:59     ` Chris King

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=14116972.post@talk.nabble.com \
    --to=mikehogan62@gmail.com \
    --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).