It depends on how you view memory. It grows 'down' if you start with address FFFFFFFF to 00000000. It grows 'up' if you start with 0000000 to FFFFFFFF. I like the latter, because 0 is always the origin. So therefor the stack grows 'up' towards the heap and .code/.text section of the process.
Akaki Kvantaliani no, the stack pointer is only used to locate the stack. there are only a few registers to store values in. so we need a "stack" where we can store all our values. the registers get overwrited all the time, but the stack sholdnt.
Very well explained, thank you!!
I'm coding for ARM7TDMI, so the instructions are a bit different, but that was still very useful and very clear :) Thanks!
Amazing explanation
I don't understand shit. Now I understand stuff
But... doesn't the stack grow down? So 1st address for example 200, next 199 etc.
It depends on how you view memory. It grows 'down' if you start with address FFFFFFFF to 00000000. It grows 'up' if you start with 0000000 to FFFFFFFF. I like the latter, because 0 is always the origin. So therefor the stack grows 'up' towards the heap and .code/.text section of the process.
Well explain
Thank you!!!!
Question:Wasn't it possible to store r1 value in r15 directly?
Akaki Kvantaliani no, the stack pointer is only used to locate the stack. there are only a few registers to store values in. so we need a "stack" where we can store all our values. the registers get overwrited all the time, but the stack sholdnt.
will this work for the MARIE simulator?
what assembly language is this?
looks like PowerPC or ARM
whats that 8bit 16bit? u can google the register names and find out wich name matches 8bit or 16bit
this is the assembly language from harvey mudd
Thanks for not having an accent