You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: Due to issues in how the perf website generates its output and
17
+
fails to deal with certain git histories, we have two different base
18
+
summaries.
19
+
20
+
Base Revision range: [170d6cb8..749f80ab](https://perf.rust-lang.org/?start=170d6cb845c8c3f0dcec5cdd4210df9ecf990244&end=749f80ab051aa0b3724b464130440b0e70a975ac&absolute=false&stat=instructions%3Au)
Base Revision range: [506f22b4..4cadeda9](https://perf.rust-lang.org/?start=506f22b4663f3e756e1e6a4f66c6309fdc00819c&end=4cadeda932d5c261a9a0b1bbd25c4486e4e0a4c6&absolute=false&stat=instructions%3Au)
* This was flagged solely because of the *number* of secondary benchmarks that were affected.
76
+
* Marking as triaged.
77
+
44
78
#### Improvements
45
79
46
-
(nothing of note)
80
+
[perf] skip normalizing param env if it is already normalized [#130561](https://github.com/rust-lang/rust/pull/130561)[(Comparison Link)](https://perf.rust-lang.org/compare.html?start=506f22b4663f3e756e1e6a4f66c6309fdc00819c&end=5793a9e90289382e447f5bc411cab2bc01c5836f&stat=instructions:u)
* There was some surprise here for the PR author because this was an allow-by-default lint and so they didn't expect it to have any actual perf impact,
187
+
because they assumed that allowed-linted could be skipped (which is not actually the way they work today, but there are PR's in process that try
188
+
to get that effect).
189
+
* In any case, this PR was flagged solely because of the *number* of secondary benchmarks that were affected.
190
+
* Marking as triaged.
191
+
192
+
Rework `non_local_definitions` lint to only use a syntactic heuristic [#127117](https://github.com/rust-lang/rust/pull/127117)[(Comparison Link)](https://perf.rust-lang.org/compare.html?start=35daf8b8aa95dee4296bad117c4cb7ecaea7bf4f&end=f5cd2c5888011d4d80311e5b771c6da507d860dd&stat=instructions:u)
* as noted by Urgau: "the version of diesel used by `rustc-perf` is too old and use named `const AA` items instead of un-named `const _` items, making the lint trigger many times (more than 150 times last time). We ruled in the past that given the regression where located in one benchmark only, and only a pathological case that the regressions where fine."
0 commit comments