"Hamish Guthrie" <hamishl at dplanet.ch> writes:
> 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?
romcc inlines everything so function nesting depth is not a problem
as there is no return state.
romcc keeps track of which variables have live values and so there is
a limit on the total number of live values (8 unless you have sse or
mmx registers).
Eric