memory organisation

[jpc]

first impression is that ram-usage is great improvement , would be helpfull to know the strategy followed by the compiler : global var's seem to grow up starting 0x900 , locals are ??? ( show 0xFFFFFFFF in statistics ) I assume that is caused by the optimiser , these must be created in soem stack-space. If declared static they show up like global's. When using a local array i found it possible to compile without error something resulting in 158% used RAM , seems this stack-space is not checked properly at the moment )

mE , can you explain how everything is/should be mapped and what are the limit's of these area's .

[pizon]

first impression is that ram-usage is great improvement , would be helpfull to know the strategy followed by the compiler : global var's seem to grow up starting 0x900 , locals are ???

Locals are on the local frame, which exists on the stack during the execution of a certain function. The W14 register is used as a frame pointer (through the LNK and ULNK instructions).

If declared static they show up like global's.

All statics are declared in the (global) data space, with local scope.

When using a local array i found it possible to compile without error something resulting in 158% used RAM , seems this stack-space is not checked properly at the moment )

Yes, statistics need some furnishing .

mE , can you explain how everything is/should be mapped and what are the limit's of these area's .

The way it is now in the .mlk file, global variables start from 0x800, and stack goes from 0x900.
this is how it is mapped now, whether it should be mapped that way is to be discussed.