[comp.sys.transputer] ROMable code from 3L C compiler

rando@skipper.dfrf.nasa.gov (Randy Brumbaugh) (08/13/90)

Has anybody generated ROMable (as in boot-from-ROM)
code from the 3L C compiler?  If so, how?

I am guesing that the code that comes out of the compiler 
and linker is position independent, and the configurer 
assigns absolute memory location.  Only a guess  -- anybody
know for sure?

Is the generated code generally relocatable (ie uses
relative addressing)?

How complicated is the configurer?  Would it be possible
to write something similar, which places the code in ROM
and the vars in RAM?

Any answers or advice would be greatly appreciated.

Thanks,
  Randy Brumbaugh
  rando@skipper.dfrf.nasa.gov

mmp@threel.co.uk (Marion Peat) (08/14/90)

>Has anybody generated ROMable (as in boot-from-ROM)
>code from the 3L C compiler?  If so, how?
>

As requested, we are broadcasting this reply to the network.

3L has a ROM Configurer package which enables embedded systems to be
configured and prepared for burning into ROM.

The package is compatible with all 3L parallel compilers: C, Fortran and Pascal.

The ROM Configurer works in a similar way to the other 3L configurers, with
the configuration file describing the target transputer network of processors,
links and connections.

The code that comes out of the compiler and linker _is_ position-independent,
as is the output from the configurer.

Please let me know if you would like a copy of the Software Product
Description or if you have any other specific questions.

 --- Marion Peat, 3L Quality Assurance Manager