Re: Different Strokes for Different Folks

"Patrick T. Homer" <patrick@cs.arizona.edu>
Fri, 15 Jan 1993 21:56:56 GMT

          From comp.compilers

Related articles
Assessing a language nharvey@probitas.cs.utas.edu.au (1993-01-06)
Re: Different Strokes for Different Folks (Was: Assessing a language) purtilo@cs.umd.edu (1993-01-07)
Re: Different Strokes for Different Folks patrick@cs.arizona.edu (Patrick T. Homer) (1993-01-15)
| List of all articles for this month |
Newsgroups: comp.compilers
From: "Patrick T. Homer" <patrick@cs.arizona.edu>
Organization: Compilers Central
Date: Fri, 15 Jan 1993 21:56:56 GMT
References: 93-01-016 93-01-031
Keywords: design



purtilo@cs.umd.edu (Jim Purtilo) replied (in part):
> Some folks down at U Arizona produced a system for mixed language
> programming (called it MLP), written up in TSE and saw some distribution...


We here at The U. of Arizona are still involved in this work. ("We" being
the same advisor, different grad students :-) We have a system called
Schooner, an extension to the MLP work written up in TSE. We are
exploring problems of heterogeneity in scientific applications, and are
currently working with NASA Lewis Research Center as part of the NPSS
project. From a heterogeneity standpoint, the work is currently focused
on connecting different architectures to take advantage of the differing
programming models available. (We support language heterogeneity as well,
but are finding most work in the scientific community is in Fortran. That
doesn't leave a lot of use at present for our ability to support multiple
languages.) We are seeking not so much to speed-up the application, as to
allow applications to be connected in new ways. The idea being to provide
a seamless program where the user is not aware of the existence of
multiple codes within the program. Our goal is to simplify the task of
the application writer who wishes to join applications together to build
such seamless programs. In this context, heterogeneity is seen as an
advantage -- allowing the user to access the best machine for each
algorithm in the program without having to worry about the language
needed, data format conversions, etc.


Patrick Homer, patrick@cs.arizona.edu
PhD student
Dept. of Computer Science
The U. of Arizona
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.