Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!mcsun!hp4nl!dutrun!dutncp8!rob From: rob@dutncp8.tudelft.nl (Rob Kurver) Newsgroups: comp.sys.transputer Subject: Re: (none) Message-ID: Date: 23 Aug 90 17:22:17 GMT References: <12563.9008231102@buck.ac.uk> Sender: news@dutrun.UUCP Lines: 29 Organisation: Delft University of Technology, The Netherlands In <12563.9008231102@buck.ac.uk> ian@buckingham.ac.uk (Ian East) writes: >Everyone seems to assume the T400 is a "stripped down" T414. However, I >wasted a lot of time to discover that MemStart for the T400 is the same >as that for a T8! Which leaves me two questions... I'm not sure I understand why you wanna know the value of MemStart? Doesn't the compiler/linker/loader/booter/OS take care if this for you? >1. Ok it states the correct MemStart in the T400 data sheet but why not > warn people LOUDLY that they must compile for T8? This is the sort of > thing that really pisses people off. If you compile for T8, the compiler starts emitting FP instructions. Clearly not wanted if the chip doesn't have these (and doesn't even trap on them)... >2. How does the debugger find out the correct value of MemStart? Is there > a hidden location or some test that works? Boot the transputer with a little program. Find the address this program is loaded at (using ldpi). This tells you the value of MemStart. That's how my debugger does it, anyways. -- Rob Kurver rob@dutncp8.tudelft.nl Computational Physics Group rob@pact.nl Faculty of Applied Physics, Delft University of Technology The moving cursor writes, and having written, blinks on.