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.

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

Use a single memory region #685

Closed
eholk opened this issue Jul 14, 2011 · 1 comment
Closed

Use a single memory region #685

eholk opened this issue Jul 14, 2011 · 1 comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@eholk
Copy link
Contributor

eholk commented Jul 14, 2011

The current memory accounting stuff is going to have a lot of problems when we start moving heap-allocated values between tasks. We should simplify it by sharing the same memory region everywhere.

@ghost ghost assigned eholk Jul 14, 2011
@eholk
Copy link
Contributor Author

eholk commented Aug 17, 2011

It's actually not too hard to transfer ownership, we're doing it now for spawn. Therefore, I'm deeming this bug WONTFIX for now.

@eholk eholk closed this as completed Aug 17, 2011
@eholk eholk removed their assignment Jun 16, 2014
pdietl pushed a commit to pdietl/rust that referenced this issue Apr 23, 2020
Remove the warning that appears on every page.
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
We can't land proper tests for the link restrictions feature until the CBMC release is out (RMC issue rust-lang#671), but we should at least build the code. Fix build and add to regression script.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Development

No branches or pull requests

1 participant