<div dir="ltr"><div>John, good day.</div><div><br></div>> I'd suggest (based on DSP experience) that, if you allow procedures to be marked for fast RAM, <div>> you restrict such marking to leaf procedures.<br></div><div><br></div><div>We have not seen yet the exact scope of work that needs to be done fast. This is a data gathering , with perhaps some DSP, application. So lets wait and see first. </div><div>Your suggestion is valuable though, if this is at all possible.</div><div><br></div><div>A question:</div><div>how did you handle the stack between slow and fast execution parts of the program? Or did it run in separate threads, making the stack business automatic?</div><div>You see, I know zippo about embedded DSP. Have you got a link to some data sheet / application notes perhaps?</div><div><br></div><div>cheers,</div><div><br></div><div>j.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 29, 2015 at 1:40 PM, John R. Strohm <span dir="ltr"><<a href="mailto:strohm@airmail.net" target="_blank">strohm@airmail.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">--- <a href="mailto:PeterMatthias@web.de">PeterMatthias@web.de</a> wrote:<br>
> Until a generalized solution is found I would simply scan for the module<br>
> names in linker that need code and/or data in fast ram and allocate it<br>
> there. A generalized solution would be to mark code/date in a special<br>
> way and let the linker do the allocation automatically.<br>
<br>
In one of the later versions of the Oberon compiler, Prof. Wirth added a special mark to denote leaf procedures. This kinda bugged me, as the compiler can easily determine whether a procedure is a leaf procedure or not, but it makes sense if you are writing a quick-and-dirty one-pass generate-IMMEDIATELY compiler, as opposed to building an abstract syntax tree and waiting until you have the entire procedure in front of you and can generate the code for it all at once.<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
--John R. Strohm<br>
<br>
--<br>
<a href="mailto:Oberon@lists.inf.ethz.ch">Oberon@lists.inf.ethz.ch</a> mailing list for ETH Oberon and related systems<br>
<a href="https://lists.inf.ethz.ch/mailman/listinfo/oberon" rel="noreferrer" target="_blank">https://lists.inf.ethz.ch/mailman/listinfo/oberon</a><br>
</blockquote></div><br></div>