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

core: unstable::global::get_global_state: Rewrite more of the runtime in Rust #4728

Closed
catamorphism opened this issue Feb 1, 2013 · 2 comments
Closed

core: unstable::global::get_global_state: Rewrite more of the runtime in Rust #4728

catamorphism opened this issue Feb 1, 2013 · 2 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

@catamorphism
Copy link
Contributor

I was surprised there wasn't already an umbrella issue for this... or maybe I'm not seeing it.
@pnkfelix
Copy link
Member

The bug here, as I understand it, is that get_global_state is using some unsafe pointer manipulation with an atomic_cxchg to install a task-global lookup table.

I do not see why this is assigned to maturity milestone #2: backwards compatibility.

It strikes me as just an enhancement to the code base. Tagging as I-nominated, and suggest we remove milestone tag entirely.

@graydon
Copy link
Contributor

graydon commented Aug 1, 2013

code in question is already deleted

@graydon graydon closed this as completed Aug 1, 2013
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
3 participants
@graydon @pnkfelix @catamorphism