Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!IRO.UMontreal.CA!matrox!altitude!Chucla!stephane From: stephane@Chucla.CAM.ORG (Stephane Laroche) Newsgroups: comp.sys.amiga.programmer Subject: Re: "chip" qualifier for Aztec C (V5.0d)? Message-ID: Date: 20 Apr 91 00:48:40 GMT References: <21925@shlump.nac.dec.com> Organization: INCA Society, Montreal, Canada Lines: 24 In article (Matthew Dillon) writes: >In article <2492@fornax.UUCP> laughlin@fornax.UUCP (Bob Laughlin) writes: >> >>One way to force screen data into CHIP ram is to use the +cd linker >>option with Manx 5.0d. This puts all initialized data into CHIP memory. >>If the initialized data in your program is largely image data then this >>is a reasonable alternative and is preferable to AllocMem'ing CHIP mem >>and copying it over. Manx 5.0d does need the chip keyword though. >>-- >> Bob Laughlin laughlin@cs.sfu.ca > > That's unreasonable, CHIP memory is at a premium these days. Only > the actual *bitmaps* need to be in CHIP. It's unreasonable unless you put all your image data in the same file (or in multiple files) and only use the +cd option on those files. This is equivalent to the _chip keyword as long as you don't mix non-chip data with chip data. > -Matt Stephane Laroche | stephane@Chucla.CAM.ORG | Montreal, Qc. CANADA +1 514 277-8605 | laroche@ee470.ee.mcgill.ca | McGill University