Re: [WP34S] Stack size impact on speed? SSIZE4. Message #2 Posted by Les Wright on 12 May 2012, 12:12 a.m., in response to message #1 by Chris Tvergard
SSIZE4 is the default. You don't have to call anything unless SSIZE8 was set by you or a program.
Keep in mind that besides the 112 dedicated registers (00-99, XYZT, A-D, I-L), you can access even more registers by indirection (and the first 16 of them directly) by allocating them via the LocR command. You are restricted to 256 registers in total (global numbered, stack, lettered, locally declared), but this is often less if RAM is used by program lines, stats registers if a stats summation has begun and the dedicated registers have not been deallocated by CLSigma, you have DBLON set, etc.
This is discussed in Appendix B and at page 20 of the most recent manual. There is even a formula to compute memory usage according to one's needs.
I would suggest that if you need to maximize your register usage, you store and run your program from the flash library, where there is gobs of program memory (over 6000 words at present), delete it and all programs from RAM so that you can access all of the registers in RAM that you can. In my opinion, it wise to learn how to assemble flash libraries from code listing for testing in the emulator before you move things onto the calculator. I would find it really frustrating to recall code to RAM for editing, save it back to flash, delete the RAM copy, retest, etc. I would sooner edit my text listing, rebuild wp34s-lib.dat, test in the emulator, and when ready concatenate the wp34s-lib.dat file to calc.bin before flashing over to the calculator. This is actually what I do with every firmware upgrade. I don't have any important programs in RAM.
Not sure what you means by "do the built-in functions benefit".
Les
|