Stack Push and Pop

Save a register to the stack and restore it.

Memory System

Semantics

The operation every function prologue performs. Whether the architecture has instructions for it, or expects the compiler to build it from ordinary stores, says a lot about how much the hardware knows about the stack.

Architecture Instructions Expressed as How this architecture does it
x86 one instruction Dedicated single-byte instructions with RSP implicit. The stack pointer is architectural, which is why the hardware can maintain a return-address predictor tied to it, and why stack pivoting is a durable exploitation technique.
ARM an idiom There is no push or pop. Prologues use STP with a pre-indexed offset, storing two registers and updating SP in one instruction, so registers are saved in pairs rather than one at a time.
RISC-V an idiom Nothing about the stack is architectural. A prologue subtracts from sp with ADDI and writes each register with an ordinary store. That sp is the stack pointer at all is an ABI convention, not something the hardware knows.
PowerISA an idiom STDU stores and updates the base register in one instruction, which is how a frame is linked to the one below it. The back-chain pointer at the bottom of every frame is an ABI convention that this instruction makes cheap. The 32-bit STWU is the same idea at word width.