GCC internally limits array sizes (in terms of bytes, not elements) to the maximum representable in a signed integer of the type specified by the back end as a SIZE_TYPE (even if that type is specified as an unsigned type, as it is in msp430). You won't be able to get arrays over 32KB in size until 20-bit integers are supported.
Peter On Mon, Apr 18, 2011 at 3:28 PM, Matthias Ringwald <matth...@ringwald.ch> wrote: > Finally, a maybe related one: I got an error trying to declare an array with > over 32k bytes/items. In my code, I can also split it into two arrays and > access them one after another, or, even assume that there's no padding bytes > in the middle, directly use FlashReadByte function. What's the reason for the > limitation? Is this a consequence of the 16-bit architecture? ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
