Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document implications of signal handling #32

Closed
sorear opened this issue May 5, 2017 · 1 comment
Closed

Document implications of signal handling #32

sorear opened this issue May 5, 2017 · 1 comment
Assignees
@sorear

Comments

@sorear
Copy link
Collaborator

sorear commented May 5, 2017

There's no red zone so the stack pointer must be decreased before any data can be stored in the frame. From openhwgroup/cv32e40p#10 .
@sorear sorear self-assigned this May 5, 2017
@aswaterman
Copy link
Contributor

Does it suffice to say that "Stack-allocated data are only persistent while the stack pointer does not exceed their addreses"?

aswaterman added a commit that referenced this issue Sep 9, 2017
@aswaterman
State assumption about stack volatility
2e966d5 
Closes #32
@aswaterman aswaterman mentioned this issue Sep 9, 2017
Merged
aswaterman added a commit that referenced this issue Sep 9, 2017
@aswaterman
State assumption about stack volatility (#43)
39e60f5 
Closes #32
@tomeksowi tomeksowi mentioned this issue May 16, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sorear sorear

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sorear @aswaterman