Remove part about stack access performance #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This part is a bit misleading. The address of stack variables is not known at compilation time, stack can be located pretty much anywhere in the address space. Local variables are accessed in the same way as memory on the heap, using their addresses (or rather by something like `[RBP + X]`, but that's not inherently faster than e.g. `[EAX]`). Using stack memory can indeed be faster, but for other reasons: - Access patterns - due to its nature, stack accesses occur repeatedly within a small area of memory, so it can be effectively cached. - Layout - due to its nature, the memory is placed close together, which again helps cached. - Allocation - stack allocation/deallocation is super simple and fast.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This part is a bit misleading. The address of stack variables is not known at compilation time, stack can be located pretty much anywhere in the address space. Local variables are accessed in the same way as memory on the heap, using their addresses (or rather by something like
[RBP + X], but that's not inherently faster than e.g.[EAX]).Using stack memory can indeed be faster, but for other reasons: