Repository navigation
Track only move paths of dropped locals in MaybeInitializedPlaces - #164434
Ramneet-Singh wants to merge 2 commits into
Conversation
|
Thanks for the pull request, and welcome! The Rust Project has assigned @jackh726 (or someone else) to review your changes, you should hear from them (or someone else) within the next two weeks. Please see the contribution instructions and our LLM policy for more information. Why was this reviewer chosen?The reviewer was selected based on:
|
|
Disclosure: An LLM was used to explore and understand the codebase, but all code here is written fresh. |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
…it, r=<try> Track only move paths of dropped locals in MaybeInitializedPlaces
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
The CI failure seems to be a Bad Gateway Error due to a network blip while fetching from the yarn package registry: Could we retry the failing check? |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (d692ff4): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @bors rollup=iffy rustc-perf Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary 1.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -2.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 488.875s -> 489.109s (0.05%) |
Drop-liveness reads only the move paths of locals that have drop points. Track only these move paths in the MaybeInitializedPlaces dataflow analysis, because a large function can have thousands of move paths which aren't required to be tracked.