Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!unmvax!polyslo!cquenel
From: cquenel@polyslo.CalPoly.EDU (-3 more school days)
Newsgroups: comp.arch
Subject: Re: front ends to crays...
Message-ID: <11874@polyslo.CalPoly.EDU>
Date: 10 Jun 89 18:28:15 GMT
References: <5674@hubcap.clemson.edu> <32216@apple.Apple.COM> <758@loligo.cc.fsu.edu> <26694@ames.arc.nasa.gov>
Reply-To: cquenel@polyslo.CalPoly.EDU (0 more school days)
Organization: Blue Blaze Irregulars
Lines: 28

In 10111 lamaster@ames.arc.nasa.gov (Hugh LaMaster) sez:
>Can you prove it is cheaper
>to copy a file to a remote machine to fix a typo than it is to fix it on
>the supercomputer?

	This could also be an argument for putting the compiler
	for your supercomputer on a "front-end".
	
	
	-- Compiling is usually not a typical "gotta have a
	   supercomputer, or it won't EVER finish" type job.
	   (At least I hope not :-) ya never know with new
	   and aggresive optimization strategies!)

	-- Assuming the compiler is written in "C" or some-such,
	   just move it over and compile it.  It should present
	   anywhere real porting problems.  The code generated is
	   the same.


--chris


-- 
@---@  -----------------------------------------------------------------  @---@
\. ./  | Chris (The Lab Rat) Quenelle      cquenel@polyslo.calpoly.edu |  \. ./
 \ /   |  You can keep my things, they've come to take me home -- PG   |   \ / 
==o==  -----------------------------------------------------------------  ==o==