D89.MIKAEL-LUNDGREN@AIDA.CSD.UU.SE (Mikael Lundgren) (03/09/90)
My question is short and simple (I hope) Can someone please tell me where I can find a Forth compiler/environment running under Unix(BSD)?
lazlor@ucscl.ucsc.EDU (Allen) (03/11/90)
I would also be interested in this information, both for an ISI 68020/68881 (BSD) and a Vax 11/750 (BSD).. Thanks -- ============================================================================== * lazlor@ucscl.UCSC.EDU - INTERNET | 'The land divided, the world united' * * ...ucbvax!ucscc!ucscl!lazlor - UUCP | Any opinions, whether implied or * * lazlor@ucscl.BITNET | expressed are not those of UCSC. * ==============================================================================
ton@hpuamsa.UUCP (Ton 't Lam AEO) (03/14/90)
I happen to see C Forth 83 This is a product of Bradley Fortware P.O. Box 4444 Mountain View, CA 94040 It runs on every Unix machine. The code is written in C is therefore very portable. My feeling is you contact Mitch Bradley for more information. Ton 't Lam The Netherlands
wmb@MITCH.ENG.SUN.COM (Mitch Bradley) (12/19/90)
> > ... spped comparison of C Forth 83 vs. assembly language Forth > > The System overheads [when running under Unix], even if you are the only > job, will matter for small sized fast benchmarks. > > Mitch, could you clarify please ? Actually, I was comparing apples to apples; C Forth 83 and the assembly language Forths were all running in the same environment (on a Sun workstation under Unix, with one user). The Unix time measurement tools separately display the time spent executing the user program and the time spent in the operating system, so you can get a good idea of what is really happening. In my experience, a good Unix implementation will not slow down a compute-bound application by more than 2 or 3 percent. This is certainly true on a Sun; it may not be true on a machine whose resources can just barely support Unix (i.e. hardware optimized (crippled?) for DOS). However, if you are running a fancy window system on a system with inadequate memory, you can see some significant slowdowns. The operating system itself is not the problem though, the problem is that you have chosen to use the machine resources for the comfort and convenience of the user. Even then, the slowdowns only occur when you are doing screen I/O, and only if you don't have enough memory (at $50/megabyte, memory is cheap; why skimp?). Presumably, when you are doing screen I/O, you are about to stop anyway (to give the user a chance to respond to the information), so even this isn't a problem. Mitch