Skip to content

Mistake in AtomicBool spinlock example #15575

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

Merged
merged 1 commit into from
Jul 11, 2014
Merged

Mistake in AtomicBool spinlock example #15575

merged 1 commit into from
Jul 11, 2014

Conversation

mvdnes
Copy link
Contributor

@mvdnes mvdnes commented Jul 10, 2014

The current example of a spinlock was not correct. The lock is actually acquired
when old == result. So we only need to deschedule when this is not the case.

The current example of a spinlock was not correct. The lock is actually acquired
when old == result. So we only need to deschedule when this is not the case.
bors added a commit that referenced this pull request Jul 11, 2014
The current example of a spinlock was not correct. The lock is actually acquired
when `old == result`. So we only need to deschedule when this is not the case.
@bors bors closed this Jul 11, 2014
@bors bors merged commit c22b22d into rust-lang:master Jul 11, 2014
@mvdnes mvdnes deleted the spinlock_error branch July 11, 2014 12:02
bors added a commit to rust-lang-ci/rust that referenced this pull request Sep 18, 2023
Intern projections in mir place

I hope this reduces mir memory usage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants