I am busy doing a port of the Geode code to V2, and am running into difficulty with the RAM sizing. The issue is not the RAM sizing itself, but the behaviour of romcc.
I have not looked into romcc in any depth at all, but am guessing that my problem results either from the declaration of too many variables or nesting function calls too deeply.
Are there any guidelines as to variable usage and function call nesting, and will romcc give any warning messages when all the registers are used up?
TIA, Hamish
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.5 - Release Date: 07.04.2005