Conversation
Avoiding the naming didn't have any meaningful perf impact.
…the few cases that used `None`
…RalfJung Avoid various uses of `Option<Span>` in favor of using `DUMMY_SP` in the few cases that used `None` based on rust-lang#122471 `DUMMY_SP` is already the sentinel value we have that says "no span". We don't need to wrap these `Span`s in a separate `Option`.
Remove fixme about LLVM basic block naming ~This may be a small perf win.~ Originally, this PR implemented the fixme, but it didn't have any measurable perf improvement. r? ``@ghost``
…haelwoerister less useless filter calls in imported_source_file This reduces calls to `filter` greatly, giving 0.3% instructions win on some tests.
add_retag: ensure box-to-raw-ptr casts are preserved for Miri In rust-lang#122233 I added `retag_box_to_raw` not realizing that we can already do `addr_of_mut!(*bx)` to turn a box into a raw pointer without an intermediate reference. We just need to ensure this information is preserved past the ElaborateBoxDerefs pass. r? ``@oli-obk``
Update the minimum external LLVM to 17 With this change, we'll have stable support for LLVM 17 and 18. For reference, the previous increase to LLVM 16 was rust-lang#117947.
…errors Do not eat nested expressions' results in `MayContainYieldPoint` format args visitor rust-lang#121563 unintentionally changed the `MayContainYieldPoint` format args visitor behavior, now missing yield points in nested expressions, as seen in rust-lang#122674. The walk can find a yield point in an expression but it was ignored. r? ``@petrochenkov`` as the reviewer of rust-lang#121563 cc ``@Jarcho`` as the author Fixes rust-lang#122674. We're in the 1.77 release week. rust-lang#121563 will land on 1.78 but beta is still 1.77.9: this PR will likely need to be backported soon after beta is cut.
add missing test: expected paren or brace in macro
Add missing `try_visit` calls in visitors.
|
@bors r+ rollup=never p=8 |
|
☀️ Test successful - checks-actions |
|
📌 Perf builds for each rolled up PR:
previous master: 3cdcdaf31b In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
A job failed! Check out the build log: (web) (plain) Click to see the possible cause of the failure (guessed by this bot) |
|
Finished benchmarking commit (d31b6fb): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression 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)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.
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 sizeResultsThis 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.
Bootstrap: 668.466s -> 667.419s (-0.16%) |
|
The big regression on @rustbot label: +perf-regression-triaged |
Successful merges:
Option<Span>in favor of usingDUMMY_SPin the few cases that usedNone#122480 (Avoid various uses ofOption<Span>in favor of usingDUMMY_SPin the few cases that usedNone)MayContainYieldPointformat args visitor #122680 (Do not eat nested expressions' results inMayContainYieldPointformat args visitor)try_visitcalls in visitors. #122689 (Add missingtry_visitcalls in visitors.)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup