[Oberon] Wojtek's comment

[Peter Matthias]

Am 29.08.2015 um 13:40 schrieb John R. Strohm:
> --- PeterMatthias at web.de wrote:
>> Until a generalized solution is found I would simply scan for the module
>> names in linker that need code and/or data in fast ram and allocate it
>> there. A generalized solution would be to mark code/date in a special
>> way and let the linker do the allocation automatically.
...
> I'd suggest (based on DSP experience) that, if you allow procedures to be marked for fast RAM, you restrict such marking to leaf procedures.
>
> The alternative is to do a transitive closure on the marked procedure: Any procedure called by a procedure marked to be located in fast RAM must also be located in fast RAM.  This is a good way to use up fast RAM very quickly, if you make one bad call decision.

Both true. However, marking code on procedure level would be difficult 
to implement. On module level it's easy to implement and can be 
restricted to leaf modules. If someone wants a stack in fast ram, 
allocate same data and let the exported procedures do the change of the 
stack pointer. Don't use exported procedures local.

> I also agree with the guy who said you want all of the fast RAM allocation information in ONE place, to make it easier to manage it all, which argues against marking individual procedures, and argues in favor of a linker control file.  I've had to do this, on a fair-sized embedded DSP project.  It was a headache and it remained an ongoing headache.

Also true. If you can't get your code into one fast ram module it gets 
complicated. If it fits, it should be easy.

Peter