-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Return a finite number of AllocIds per ConstAllocation in Miri #118336
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
2 commits
Select commit
Hold shift + click to select a range
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
// The const fn interpreter creates a new AllocId every time it evaluates any const. | ||
// If we do that in Miri, repeatedly evaluating a const causes unbounded memory use | ||
// we need to keep track of the base address for that AllocId, and the allocation is never | ||
// deallocated. | ||
// In Miri we explicitly store previously-assigned AllocIds for each const and ensure | ||
// that we only hand out a finite number of AllocIds per const. | ||
// MIR inlining will put every evaluation of the const we're repeatedly evaluting into the same | ||
// stack frame, breaking this test. | ||
//@compile-flags: -Zinline-mir=no | ||
#![feature(strict_provenance)] | ||
|
||
const EVALS: usize = 256; | ||
|
||
use std::collections::HashSet; | ||
fn main() { | ||
let mut addrs = HashSet::new(); | ||
for _ in 0..EVALS { | ||
addrs.insert(const_addr()); | ||
} | ||
// Check that the const allocation has multiple base addresses | ||
assert!(addrs.len() > 1); | ||
// But also that we get a limited number of unique base addresses | ||
assert!(addrs.len() < EVALS); | ||
|
||
// Check that within a call we always produce the same address | ||
let mut prev = 0; | ||
for iter in 0..EVALS { | ||
let addr = "test".as_bytes().as_ptr().addr(); | ||
if iter > 0 { | ||
assert_eq!(prev, addr); | ||
} | ||
prev = addr; | ||
} | ||
} | ||
|
||
fn const_addr() -> usize { | ||
"test".as_bytes().as_ptr().addr() | ||
} |
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.
Uh oh!
There was an error while loading. Please reload this page.