Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!overload!dillon From: dillon@overload.Berkeley.CA.US (Matthew Dillon) Newsgroups: comp.sys.amiga.programmer Subject: Re: "chip" qualifier for Aztec C (V5.0d)? Message-ID: Date: 15 Apr 91 19:22:36 GMT References: <21925@shlump.nac.dec.com> <41242@cup.portal.com> <2492@fornax.UUCP> Organization: Not an Organization Lines: 27 In article <2492@fornax.UUCP> laughlin@fornax.UUCP (Bob Laughlin) writes: >In article <41242@cup.portal.com> plav@cup.portal.com (Rick M Plavnicky) writes: >> ......... >>This comes up every so often. Manx currently does NOT offer the ``chip'' >>keyword in their product. (Current product is referred to as 5.0e, but >>signs on as 5.0d dated Sep 30 1990) >> ......... > >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 -- Matthew Dillon dillon@Overload.Berkeley.CA.US 891 Regal Rd. uunet.uu.net!overload!dillon Berkeley, Ca. 94708 USA