9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan9 on the Cell...
Date: Sat, 28 May 2005 11:56:54 -0600	[thread overview]
Message-ID: <Pine.LNX.4.58.0505281151050.21084@enigma.lanl.gov> (raw)
In-Reply-To: <Pine.LNX.4.58.0505281142450.21084@enigma.lanl.gov>

Actually, I learned a good bit more about the whole Cell situation this
morning, from the chipset level on up to the 'when will systems get out'
level. The situation is, to say the least, murky, and will be for a while.

However: If we were to put effort into a G5 port, which is cheap to do
(buy a mac!), we'd be ready to rock and roll on the Cell when systems 
become more generally available. 

So, Plan 9 is getting fixed for 64-bit mode, we have a K8 compiler now as 
a template. What do we name the compiler?

Cell C (or cc)? Just joking!

G5 C or gc? I'll stop now.

ron



  reply	other threads:[~2005-05-28 17:56 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 19:05 Paul Lalonde
2005-05-24 19:26 ` Eric Van Hensbergen
2005-05-24 23:04   ` Paul Lalonde
2005-05-24 23:18     ` Jack Johnson
2005-05-24 23:27       ` Eric Van Hensbergen
2005-05-24 23:30       ` Paul Lalonde
2005-05-25  3:11         ` Bruce Ellis
2005-05-27 16:53         ` Paul Lalonde
2005-05-28  6:29           ` andrey mirtchovski
2005-05-28 14:51             ` Eric Van Hensbergen
2005-05-28 17:45             ` Ronald G. Minnich
2005-05-28 17:56               ` Ronald G. Minnich [this message]
2005-05-28 18:11                 ` Jack Johnson
2005-05-28 18:31                   ` jmk
2005-05-28 18:34                 ` Paul Lalonde
2005-05-29  6:35                 ` Noah Evans
2005-05-29  9:26                   ` Charles Forsyth
2005-05-30 20:43                     ` Eric Van Hensbergen
2005-06-03 11:55                   ` Noah Evans
2005-06-03 12:57                     ` Eric Van Hensbergen
2005-06-03 15:46                     ` Dave Eckhardt
2005-06-03 16:43                       ` Ronald G. Minnich
2005-06-03 17:33                         ` Brantley Coile
2005-06-03 21:22                         ` David Leimbach
2005-05-29  9:26                 ` Charles Forsyth
2005-05-24 23:26     ` Eric Van Hensbergen
2005-05-25  9:10       ` C H Forsyth
2005-05-25 15:07         ` Ronald G. Minnich
     [not found]           ` <a4e6962a050525081244ed619d@mail.gmail.com>
2005-05-25 15:13             ` Fwd: " Eric Van Hensbergen
2005-05-25 15:30           ` C H Forsyth
2005-06-21 16:46   ` Eric Van Hensbergen
2005-06-10 14:04 ` Eric Van Hensbergen
2005-06-10 16:44   ` Paul Lalonde
2005-06-10 18:43     ` Bruce Ellis
2005-06-11  3:17     ` Ronald G. Minnich
2005-06-11  3:38       ` Tim Newsham
2005-06-11  3:45         ` Ronald G. Minnich
2005-06-11 19:36           ` C H Forsyth
2005-06-12 21:36       ` arisawa
2005-06-12 22:55         ` Eric Van Hensbergen
2005-06-12 23:54           ` George Gensure
2005-06-13  2:39         ` Ronald G. Minnich
2005-06-13  5:17           ` Martin C. Atkins
2005-05-28 19:21 jmk

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=Pine.LNX.4.58.0505281151050.21084@enigma.lanl.gov \
    --to=rminnich@lanl.gov \
    --cc=9fans@cse.psu.edu \
    /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).