| title |
Stack Usage | Microsoft Docs |
| ms.custom |
|
| ms.date |
11/04/2016 |
| ms.reviewer |
|
| ms.suite |
|
| ms.technology |
|
| ms.tgt_pltfrm |
|
| ms.topic |
article |
| dev_langs |
|
| ms.assetid |
383f0072-0438-489f-8829-cca89582408c |
| caps.latest.revision |
9 |
| author |
corob-msft |
| ms.author |
corob |
| manager |
ghogen |
| translation.priority.ht |
cs-cz |
de-de |
es-es |
fr-fr |
it-it |
ja-jp |
ko-kr |
pl-pl |
pt-br |
ru-ru |
tr-tr |
zh-cn |
zh-tw |
|
| translationtype |
Human Translation |
| ms.sourcegitcommit |
3168772cbb7e8127523bc2fc2da5cc9b4f59beb8 |
| ms.openlocfilehash |
cc44b6968e03257d8d5c7a417e4a3fca187d4071 |
All memory beyond the current address of RSP is considered volatile: The OS, or a debugger, may overwrite this memory during a user debug session, or an interrupt handler. Thus, RSP must always be set before attempting to read or write values to a stack frame.
This section discusses the allocation of stack space for local variables and the alloca intrinsic.
x64 Software Conventions