How does stack work in a CPU? Why do we need it?

[@thegt]

One of the best explanations I've seen so far. Enough level of detalization, good level of visualization.

[@darkmadarauchiha]

Really useful video, watched a few others but they didn't help much. You started at the right level to help everything else fall into place! Keep it up!

[@muhammedazoz]

Awesome explanation 🔝

[@egotraumatic]

Better to watch on x1.5. Great video! Thank you!

[@joerit633]

Excellent video!! Very interesting and informative!! Thank you!!!!

[@abhijitbaruah2207]

one of the best video

[@mikhailmikheev8043]

youtube algorithm doing wonders

[@aeleee]

best ever

[@noa29Enib]

Great explanations thanks :)

[@TON-vz3pe]

Fantastic explanation. But where does the text segment fits in all this?

[@0x20d]

I assume you mean the text segment in your assembly file? If so, the text segment holds your instructions. In case of this example that would be j=j+k (or EAX

[@user-hk4cu5go9c]

The text segment is a memory segment of a process which contains the instructions of that process. Thus, the IP points to instructions in the text segment which, when pointing to functions being called, invokes function stack frames to be created on the stack (and hence the increment/decrement of the stack pointer). Hope that makes sense, assuming I've understood your question correctly lol.

[@krenilraj4180]

can someone explain me , the foo() function in the white diagram is the instruction there and foo stack frame , a stack is created for foo function inside there variables are stored and after it is successfully loaded it will CPU will start executing foo function Am I right ? If wrong please explain me

[@user-hk4cu5go9c]

Yes, you are correct. Once the foo() function has finished executing on the CPU, the stack pointer is incremented to a higher memory address back to the top of main's stack frame and foo's stack frame is popped off. Remember, the stack pointer gets INCREMENTED because the stack grows downards towards lower memory addresses, hence any stack frames being popped cause the pointer to point to the previous stack frame's HIGHER memory address.

[@Jkauppa]

why not just direct in-memory computing

[@yuriyfse6555]

))) how you imagine it?)

[@tsunningwah3471]

zhina!!!!!

[@yuriyfse6555]

ma-an, very slowly it's 2023 on yard, not 1960 - in youtube we can watch many different videos