From: "Steven D. Vormwald" <sdvormwa@mtu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 on Blue Gene
Date: Wed, 30 Jul 2008 12:10:31 -0400 [thread overview]
Message-ID: <48909277.2010602@mtu.edu> (raw)
In-Reply-To: <13426df10807300841y1e4bed36l7a009c8873f39c1b@mail.gmail.com>
ron minnich wrote:
> On Wed, Jul 30, 2008 at 8:21 AM, Steven D. Vormwald <sdvormwa@mtu.edu> wrote:
>
>> So would developers on this platform be encouraged to use languages and
>> features currently in plan 9 for HPC development, or would they target
>> existing HPC languages and features, which would be added to plan 9, either
>> via native ports or some kind of compatibility layer?
>
> The latter. Build on Linux, run on Plan 9. For most users. Some users
> have the time and willingness to try something new like Plan 9, most
> have day jobs and just want to run their code. So we make it as easy
> for them as we can.
>
Since I still do most of my work on Linux, I can't really argue with
that... ;)
>> I noticed that a
>> limited version of MPI was mentioned in one of the papers on IBM's website,
>> but what about other systems, such as Co-Array fortran or UPC?
>>
>
> Cross-compile.
>
> ron
>
Correct me if I'm wrong here, but don't these require extensive run-time
support, in addition to compiler support? Will the run-time libraries
also be linux libraries running under a compatibility layer?
Steven Vormwald
next prev parent reply other threads:[~2008-07-30 16:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 18:37 Steven Vormwald
2008-07-26 18:47 ` Eric Van Hensbergen
2008-07-30 12:32 ` Roman V. Shaposhnik
2008-07-30 14:07 ` Eric Van Hensbergen
2008-07-30 15:10 ` ron minnich
2008-07-30 15:21 ` Steven D. Vormwald
2008-07-30 15:38 ` Eric Van Hensbergen
2008-07-30 15:41 ` ron minnich
2008-07-30 16:10 ` Steven D. Vormwald [this message]
2008-07-30 17:42 ` ron minnich
2008-07-30 17:52 ` Steven D. Vormwald
2008-07-31 21:32 ` Charles Forsyth
2008-07-30 16:34 ` Joel C. Salomon
2008-07-30 15:25 ` gdiaz
2008-07-30 15:36 ` Eric Van Hensbergen
2008-07-30 23:36 ` David Leimbach
2008-07-31 0:02 ` ron minnich
2008-07-31 0:45 ` erik quanstrom
2008-07-31 1:48 ` David Leimbach
2008-07-31 2:23 ` ron minnich
2008-07-31 12:53 ` Philippe Anel
2008-07-31 13:35 ` David Leimbach
2008-07-31 14:11 ` Philippe Anel
2008-07-31 14:32 ` David Leimbach
2008-07-31 16:04 ` ron minnich
2008-08-04 23:19 ` Uriel
2008-07-31 13:24 ` gdiaz
2008-07-31 13:24 ` gdiaz
2008-07-30 15:40 ` ron minnich
2008-07-30 17:36 ` don bailey
2008-07-30 17:39 ` Benjamin Huntsman
2008-07-30 17:47 ` ron minnich
2008-07-30 18:03 ` don bailey
2008-07-30 18:08 ` Eric Van Hensbergen
2008-07-30 18:18 ` ron minnich
2008-07-30 18:21 ` erik quanstrom
2008-07-30 18:32 ` ron minnich
2008-07-31 22:03 ` Charles Forsyth
2008-07-31 22:06 ` ron minnich
2008-07-31 21:27 ` Charles Forsyth
2008-07-30 15:43 ` Jack Johnson
2008-07-31 14:01 erik quanstrom
[not found] <2049e07e918215a675b00f15ee549436@quanstro.net>
2008-07-31 14:28 ` David Leimbach
2008-07-31 15:20 ` erik quanstrom
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=48909277.2010602@mtu.edu \
--to=sdvormwa@mtu.edu \
--cc=9fans@9fans.net \
/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).