🚀 go-pugleaf

In article <735@applix.UUCP> scott@applix.UUCP (Scott Evernden) writes:
<In article <2242@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
<>I don't understand all the hoopla over CHIP RAM. The Manx linker has long
<>allowed you to specify the type of memory each file should go in...
<
<The Manx linker allows you to specify the type of memory each entire
<*program section* (text,data,bss) should go in; there is no
<per file/module control.

Perhaps Peter mis-spoke himself. That feature goes in the compiler,
not the linker. As an example, the Lattice 4 compiler allows you to
specify for each file compiled wether each of the three aformentioned
segments should be placed in chip, fast or whatever is available
memory.

So I take Peter's solution - whenver I have a file that needs a data
image in CHIP, I put the data in a seperate file, and compile it with
the -ad flag on. Viola - the data structure lands in chip memory. No
need to waste time testing to see if it's in chip, or allocating more
memory, etc.

	<mike
--
Must have walked those streets for hours,		Mike Meyer
In the dark and in the cold,				mwm@berkeley.edu
Before I really could accept,				ucbvax!mwm
There's no place called hope road.			mwm@ucbjade.BITNET