??? 03/21/05 08:34 Read: times |
#90087 - To Mehdi Responding to: ???'s previous message |
I don't know whether you are asking a question or questioning Oleg's and my logic. In placing the stack 'up top' you're freeing the memory below. If your arrays overwrite the stack - too bad. If you overrun your stack, make the stack larger. The general idea of my suggestion (and backed up by Oleg's compiler observations) is that the stack is above your variables. If you add variables to you code, then the assembler moves the stack up. Note that I use the DS (define space) pseudo op so the assembler does the allocation work for me. If you allocate to many variables and don't allow enough space for the stack - too bad! |
Topic | Author | Date |
initializing SP to 7FH | 01/01/70 00:00 | |
why? | 01/01/70 00:00 | |
To Oleg & Russell | 01/01/70 00:00 | |
To Mehdi | 01/01/70 00:00 | |
To Mehdi | 01/01/70 00:00 | |
why not | 01/01/70 00:00 | |
for example, please | 01/01/70 00:00 | |
Oleg, why I do similar | 01/01/70 00:00 | |
here they are | 01/01/70 00:00 | |
well | 01/01/70 00:00 | |
well well | 01/01/70 00:00 | |
well, well - done | 01/01/70 00:00 | |
tight SRAM - use C | 01/01/70 00:00 | |
- or assembler![]() | 01/01/70 00:00 | |
Stack pointer | 01/01/70 00:00 | |
external stack | 01/01/70 00:00 | |
why not? | 01/01/70 00:00 | |
SDCC | 01/01/70 00:00 | |
Re:initializing SP to 7FH | 01/01/70 00:00 | |
very old assemblers only | 01/01/70 00:00 | |
Let the assembler do the work! | 01/01/70 00:00 |