Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!elroy!cit-vax!oberon!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga
Subject: Re: Copying to chip RAM
Message-ID: <7953@oberon.USC.EDU>
Date: 30 Mar 88 02:28:17 GMT
References: <442@lamont.Columbia.edu> <2210@phoenix.Princeton.EDU> <7923@oberon.USC.EDU> <2221@phoenix.Princeton.EDU>
Sender: news@oberon.USC.EDU
Reply-To: papa@pollux.usc.edu (Marco Papa)
Organization: Felsina Software, Los Angeles, CA
Lines: 21

In article <2221@phoenix.Princeton.EDU| kenchiu@phoenix.Princeton.EDU (Kenneth Chiu) writes:
|In article <7923@oberon.USC.EDU| papa@pollux.usc.edu (Marco Papa) writes:
||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.
|
|Hmm. . .from my reading of my Manx manual, you can only specify location
|at the level of code, initialized data, and uninitialized data.  Thus you
|would have to put *all* of your initialized variables in CHIP, even if
|only 10% needed to be.  Am I missing something?

No, you're not. I should have been more specific: Lattice allows you to put
all or SOME data in CHIP RAM; MANX allows you to put ALL or NONE of the 
intializeed or non-initialized data in CHIP RAM. Sorry for the confusion.

-- 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]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=