home *** CD-ROM | disk | FTP | other *** search
- Path: Flex058.dBH.WAU.NL!joop.vandeWege
- From: joop.vandeWege@medew.ento.wau.nl (Joop van de Wege)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: GCC PROBLEMS?
- Date: Wed, 20 Mar 1996 09:38:10 LOCAL
- Organization: ento
- Distribution: world
- Message-ID: <joop.vandeWege.572.001ABE50@medew.ento.wau.nl>
- References: <Qx9jRAAse0SxEws3@naylor1.demon.co.uk>
- NNTP-Posting-Host: flex058.dbh.wau.nl
- X-Newsreader: Trumpet for Windows [Version 1.0 Rev B final beta #4]
-
- In article <Qx9jRAAse0SxEws3@naylor1.demon.co.uk> Chris Naylor <chris@naylor1.demon.co.uk> writes:
- >From: Chris Naylor <chris@naylor1.demon.co.uk>
- >Subject: GCC PROBLEMS?
- >Date: Sat, 16 Mar 1996 22:58:52 +0000
-
- >Can someone helpme with the following problems?
-
- >USHORT chip my_image_data[]=
- >{
- >0xE300...
- > The above is an example from the ACM manual,but fails to compile
- >with GCC and is something to do with `chip` part, obviously this
- >specifies that it should be in CHIPMEM but gcc does not reconise this
- One solution is to allocate the memory yourself in CHIP and copy the data to
- it. The other is to check out Kamil Iskra (?) http site. I think he has added
- support to gcc to recognise the chip keyword.
-
-
- >Also what do the PROTO files do.
- >How do I generate these files or dont I need to as most of the examples
- >in ROM KERNAL MANUALS seem to #include these files.
- Replace them with the corresponding #include<clib/xxxx_proto.h>
- This will take care of inlining when -O is used automatically. This hold true
- for SAS, gcc, Dice(?)
-
- Joop
-
-
- >Martin Naylor
-
-