Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!ogicse!intelhf!ichips!omews1!waggoner From: waggoner@omews1.intel.com (Mark Waggoner) Newsgroups: comp.sys.amiga.programmer Subject: Re: "chip" qualifier for Aztec C (V5.0d)? Summary: No, it doesn't have it but you can do what you want to do Message-ID: <1991Apr17.161732.27842@omews63.intel.com> Date: 17 Apr 91 16:17:32 GMT References: <21925@shlump.nac.dec.com> <41242@cup.portal.com> <2492@fornax.UUCP> Sender: news@omews63.intel.com (News Account) Reply-To: waggoner@ichips.intel.com (Mark Waggoner) Organization: Intel Corp., Hillsboro, Oregon Lines: 30 In article dillon@overload.Berkeley.CA.US (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. > -Matt You don't have to put ALL initialized data into CHIP memory. If you put the data you need in CHIP in a seperate file you can use the +cd option for that module and then switch it back to normal allocation for other modules. I don't remember the appropriate options for doing that. It is admittedly not as convenient as a _chip keyword, but you can do what you want to do. Mark Mark Waggoner waggoner@ichips.intel.com (503) 696-4590 No, I don't speak for intel.