Danny Lau said;

> a large continuously "unsigned int"
> memory array. I declare it as this: unsigned int LCD_BUFFER[320*3][240<<1].

As already pointed, it's rather obscure programming practice; easy to make
mistake(s) for both human being and machine.  It seems 240*320@16bpp does
not make any match.  Better to pursue simpler constructs to do the same thing.

Have you tried to omit GCC optimization flag (-O?) for that file in question if
exists?  -O flag triggers code optimizer to use aggressively "smart instructions"
or "insn reorder and collapse to save time and space."  This often means to
bring processor dependent extension out of stock which is less commonly used.
If compiler misunderstands the nature of target CPU, optimization ends up with
incorrect instruction.

Toru Nishimura/ALKYL Technology