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

Be precise about the stack budget #2820

Closed
brson opened this issue Jul 6, 2012 · 3 comments
Closed

Be precise about the stack budget #2820

brson opened this issue Jul 6, 2012 · 3 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot.

Comments

@brson
Copy link
Contributor

brson commented Jul 6, 2012

The calculations involved in deciding when the stack has run out are very, very imprecise. User code should be allowed to take up exactly the amount the task is configured for. This will involve discounting the red zone and any unused space before the red zone, and also ensuring that the final stack segment is configured such that the stack limit is set to the appropriate address to enforce the stack budget.
@ghost ghost assigned brson Jul 12, 2012
@nikomatsakis nikomatsakis mentioned this issue Apr 25, 2013
Closed
@emberian
Copy link
Member

Visiting for triage; still relevant. Marking E-hard as it is very non-trivial.

@emberian
Copy link
Member

@nikomatsakis @brson with the new runtime/stack work is this still relevant?

@brson
Copy link
Contributor Author

brson commented Oct 11, 2013

I guess this is kind of obsolete since the code this was referencing no longer exists.

@brson brson closed this as completed Oct 11, 2013
saethlin pushed a commit to saethlin/rust that referenced this issue Apr 11, 2023
@bors
Auto merge of rust-lang#2820 - oli-obk:rustup, r=RalfJung
ce4b118 
Have the miri cronjob link to the failed run.

Also explain what needs to be done to resolve the failing CI.
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@celinval
Fix panic warning and add arbitrary Duration (rust-lang#2820)
c89a7e7 
Add an Arbitrary implementation for Duration and also fix unused
variable warnings when panic message uses a variable in its format
string.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brson @emberian