-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
interpret: make Place always refer to the current frame [perf experiment] #113964
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt |
This comment was marked as outdated.
This comment was marked as outdated.
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit dcd018c with merge 8d2bed6d76e99526a3999cae306609362c9b7994... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (8d2bed6d76e99526a3999cae306609362c9b7994): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResultsThis 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 650.262s -> 650.688s (0.07%) |
Okay, looks like this is quite measurable in the stress test, so I guess we can keep it. We have to be careful to not switch threads at the wrong time... but then with this PR we have to be careful to not push/pop at the wrong time, so it's not like that is significantly more robust. |
The place storing a frame-idx was only a band-aid, since with concurrency we still would not have any idea which thread's stack the place refers to. So let's just accept that places must be short-lived, and use MemPlace in situations where stack frames are being pushed or popped.
This is a perf experiment.
(If perf looks good, a bit more cleanup should be done to consistently use
MPlaceTy
for the return place in the various functions for shims and hooks.)r? @ghost