griffin@frith.egr.msu.edu (02/05/90)
Private reply bounced, so... Message-Id: <9002050055.AA27337@frith.egr.msu.edu> To: waggoner@dtg.nsc.com Subject: Re: Aztec 5.0 and chip memory In-Reply-To: your article <382@icebox.nsc.com> News-Path: cps3xx!netnews.upenn.edu!rutgers!cs.utexas.edu!samsung!rex!ames!amdahl!nsc!voder!dtg.nsc.com!waggoner Yes, you can force selected portions of code into any type of memory you wish by linking with +c[cdb]. Look in the linker manual page 5-15 for more detailed info. Dan Griffin griffin@frith.egr.msu.edu "We're waiting for Godot..."
mcw@wet.UUCP (Martin Warnett) (02/09/90)
You can force executable code, inititialized data and uninitialized data into either chip or fast memory with the linker options +c and +f. There is no way to force specific variables into chip ram as in Lattice's chip keyword. A big oversight by Manx, IMHO. -- +====================================================================+ | Martin Warnett | uucp: ...sun!claris!wet!mcw | | San Francisco, CA | claris!wet!mcw@ames.arc.nasa.gov | +====================================================================+