-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Record allocation spans inside force_allocation #115184
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
Conversation
Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri The Miri subtree was changed cc @rust-lang/miri |
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.
Thanks, looks great overall with minor nits!
Can you confirm that if you use current_span
instead, at least one of the tests changes its output?
Their output does change, but not in a way that is meaningful. They highlight the span of the expression for the rvalue in the |
0019e90
to
ec21d58
Compare
Thanks! One of my comments is still unresolved I think. |
Co-authored-by: Ralf Jung <[email protected]>
Looks good, thanks! |
☀️ Test successful - checks-actions |
Finished benchmarking commit (296c7a6): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 632.601s -> 629.829s (-0.44%) |
This expands rust-lang/miri#2940 to cover locals
r? @RalfJung