Path: utzoo!mnetor!uunet!husc6!think!bloom-beacon!oberon!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga
Subject: Re: Copying to chip RAM
Message-ID: <7923@oberon.USC.EDU>
Date: 28 Mar 88 20:00:51 GMT
References: <442@lamont.Columbia.edu> <2210@phoenix.Princeton.EDU>
Sender: news@oberon.USC.EDU
Reply-To: papa@pollux.usc.edu (Marco Papa)
Organization: Felsina Software, Los Angeles, CA
Lines: 22

In article <2210@phoenix.Princeton.EDU| kenchiu@phoenix.Princeton.EDU (Kenneth Chiu) writes:
|In article <442@lamont.Columbia.edu| adam@lamont.Columbia.edu (adam levin) writes:
||I have a 'C' array which needs to be in chip RAM.  The examples I have found
||declare the array, AllocMem some chip RAM, and copy the array into it.
|
|I'm not sure of all the details, but I'm assuming that you have a lot of
|static data.  Two solutions come to mind:  (1) keep the data in a file,
|allocate a chip array, initialize from the file.  (2) create a static
|data segment, forcing everything into chip, then LoadSeg() it.  Neither
|solution is very elegant.  Compilers need another storage class.

Both Lattice C and MANX C have link-time switches that allow you pto ut all
or some of the data in a hunk that will be loaded in CHIP memory.  Details
in the manuals.

-- Marco Papa

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
uucp:...!pollux!papa       BIX:papa       ARPAnet:pollux!papa@oberon.usc.edu

 "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=