-
Notifications
You must be signed in to change notification settings - Fork 13k
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
~, ~[] and ~str not containing @ shouldn't have gc headers #5026
Comments
Not critical for 0.7. Nominating for milestone 5 (production-ready). |
Yeah, performance sadness is a production ready thing. Accepted. |
This is recently in progress by @thestinger |
I landed #7495 and #7521 with the initial work on this. There's no longer anything reading/writing to the exchange allocation headers (on ~T and ~[]) and they are no longer initialized. I really don't know enough about trans to finish this off by myself. I have work started here: https://github.com/thestinger/rust/commits/vec but I'm not having much luck tracking down and fixing the remaining issues. |
Track me down more often once we've got 0.7 out, I know a lot of the awkward bits on this |
This is now done for ~T. I'm going to open a new bug about ~[]/~str (already have #7496 for ~fn). |
…ring-fences, r=phansch Detect usage of invalid atomic ordering in memory fences Detect usage of `core::sync::atomic::{fence, compiler_fence}` with `Ordering::Relaxed` and suggest valid alternatives. changelog: Extend `invalid_atomic_ordering` to lint memory fences Fixes rust-lang#5026
There's a 4-word header added to every owned pointer right now:
The text was updated successfully, but these errors were encountered: