Newsgroups: comp.sys.transputer
From: jan@neuroinformatik.ruhr-uni-bochum.de (Jan Vorbrueggen)
Subject: Re: HELP problem porting ANSI C from HP-UX to single transputer!
Organization: Institut fuer Neuroinformatik, Ruhr-Universitaet Bochum, Germany
Date: 22 Oct 94 11:19:41 GMT
Message-ID: <JAN.94Oct22121941@thalia.neuroinformatik.ruhr-uni-bochum.de>

In article <387p92$shd@fang.dsto.gov.au> nickt@ewd.dsto.gov.au (Nick Taransky)
writes:

   inmos C toolset: IMS D7214C (documentation Aug 1990, discs 25 Jun 1991)

This is seriously out of date, I think. Especially if you want to have an
easier job programming multiple processors, the later versions inlcude the VCR
in the collector (or does that work only for occam2 programmes??).

   The problem does not seem to be related to the size of the data being
   processedor the size of the object code of the complied modules. It seems
   that a code pointer is being over written or some other problem of this
   type is occurring. I am reasonably confident that errors have not been made
   in pointer arithmetic.

From my limited experience with C on transputer, check two things:

- Have you compiled with heap/stack checking enabled? Otherwise, you'll run
out of 'em without noticing until much later...
- I'm not sure whether NULL is numerically equal to 0. The natural value on
transputers would be #80000000, but I think Inmos changed that so customers
wouldn't be too confused...anyway, here's another possibility for getting
things mixed up.

	Jan

