ushort chip on 1.3 in DICE 3.16 -already answered

[desiv]

OK, I was having an issue, but found the solution...
(After I typed most of this, but before I clicked Submit and found something in an Amiga C book that made me look at the dcc (DICE compiler) doc files closer... )

Spoiler, the solution is: "__chip USHORT" instead of "USHORT chip".

----
The Amiga C Manual (disk 1, example 7) uses this type of data block for their image data:

/* REMEMBER! Image data MUST be put in chip-memory! */
USHORT chip my_image_data[]= /* Image data for a nice four colour face: */
{
  0x3E00, /* Bitplane ZERO */
  0x7F00,
  0xC980
...
...

But when I try to compile this with DICE, it gives me an error.
I was able to get it to compile and run (on an AmigaForever 2M CHIP A500 config that matches my physical A500), but by doing this:

USHORT my_image_data[]=

So, I had to take out the "chip" directive...
------

And as mentioned, the solution was to use the __chip in FRONT of the USHORT instead of just chip after it...

I wish I could find my .h file to see what I had used back in the day. Did a different version of DICE change that? Different version of the Amiga C Manual code?
Or did I just read the manual better 30+ years ago...
(Doubtful, but then again the printed code I found had WAY more commenting that I ever thought I would do... ;-)

[Thomas Richter]

The original example was never valid C syntax, so I wonder which compiler should have accepted this code snippet.

[desiv]

Originally Posted by Thomas Richter

The original example was never valid C syntax, so I wonder which compiler should have accepted this code snippet.

Interesting... I've seen several other mentions online of the code in the ACM not being ideal (no prototyping (which I still haven't looked at and don't really know what that is... ;-) ).
I just took a look, and it looks like the author was using Lattice C.
From the ACM intro chapter:

If you use the Lattice C Compiler V5.00 or higher, you can put the keyword "chip" in front of the name of the data, and the Compiler will automatically put it in the Chip Memory.
Eg. UWORD chip graphics_data[] = { ... };

As I only used DICE back in the day and my code was inspired/based on the ACM examples, I almost certainly ran across that at the time and forgot in the last 32 years... ;-)