forked from rust-lang/rust
-
Notifications
You must be signed in to change notification settings - Fork 3
Remove precise box allocation #36
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
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
af3aaf3
Remove precise allocation for Box
jacob-hughes 711d75e
Turn on untraceable allocation by default
jacob-hughes 4928862
Remove runtime branch during allocation
jacob-hughes fffcbdc
Expand types which can be safely allocated as untraceable
jacob-hughes 45f42b7
Make Gc::new() alloc untraceable by default
jacob-hughes File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
// | ||
// ignore-test | ||
// min-llvm-version: 10.0.1 | ||
// compile-flags: -O | ||
#![crate_type="lib"] | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
// run-pass | ||
#![feature(gc)] | ||
#![allow(dead_code)] | ||
|
||
use std::gc::needs_tracing; | ||
use std::rc::Rc; | ||
use std::cell::Cell; | ||
|
||
|
||
struct A { | ||
inner1: B, | ||
inner2: *mut u8 | ||
} | ||
|
||
enum B { | ||
W(Vec<C>), | ||
X((usize, Vec<C>)), | ||
Y(Vec<B>), | ||
Z(String), | ||
} | ||
|
||
struct C { | ||
a: Rc<usize>, | ||
b: Cell<usize> | ||
} | ||
|
||
struct D(Vec<A>); | ||
|
||
const CONST_A: bool = needs_tracing::<A>(); | ||
const CONST_B: bool = needs_tracing::<B>(); | ||
const CONST_C: bool = needs_tracing::<C>(); | ||
const CONST_D: bool = needs_tracing::<D>(); | ||
|
||
fn main() { | ||
assert!(CONST_A); | ||
assert!(!CONST_B); | ||
assert!(!CONST_C); | ||
assert!(CONST_D); | ||
} |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what this comment is supposed to be attached to (presumably the second clause?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rustc has a lint which won't allow an unsafe block without a comment explaining why the unsafe block is ok to use.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh! Would it be clearer to write this as:
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree this is better and I went to change it, but then
x.py fmt
reverted my changes. I think we should leave it because fighting with the formatter is just going to cause pain.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it reverts it, I don't think we have much choice :)