Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!mcsun!unido!infbs!tubsibr!schoenfr
From: schoenfr@tubsibr.uucp (Erik Schoenfelder)
Newsgroups: comp.sys.transputer
Subject: Re: GNU C for the transputer
Message-ID: <1989Oct23.152443.22366@tubsibr.uucp>
Date: 23 Oct 89 15:24:43 GMT
References: <8910192040.AA20132@topologix.com>
Organization: TU Braunschweig, W. Germany
Lines: 25

In article <8910192040.AA20132@topologix.com> andy@topologix.UUCP 
(Andy Pfiffer) writes:

Andy>   The problem with using the on-chip RAM as register variables
Andy>   is that if you want more than one GCC-produced binary running
Andy>   on the Transputer at a time, you have introduced a management
Andy>   problem; you must now context-switch on-chip RAM (or portions
Andy>   of it) between processes.

Yes, you are right.

Andy>	A better solution might be to design a new Transputer ...

Andy>	The best solution might be to throw an R3000*, an R3010*, two
Andy>	8-channel NCR-SCSI Sripts processors, a Virtual-Cut-Through
Andy>	router, and a few 100Mb/sec FDDI controllers into a centrifuge
Andy>	and pour the resulting goo into a 12x12 PGA.

And - don't forget to disconnect the transputer boards: We won't slow
the system down.

Erik
--
Trillium ?