Skip to content

Conversation

Enselic
Copy link
Member

@Enselic Enselic commented Jan 1, 2024

This reverts commit 231dbbc. It regressed performance. See #119251.

It is not a pure revert because we also need to allow rustc::potential_query_instability in one more place now because of the revert.

r? @cjgillot

FWIW, I have tried to find a way in which the loop iterates over more than one lint (which is needed in order for the non-determinism to matter), but so far I have not found a way.

… `&FxIndexMap`"

This reverts commit 231dbbc.
It regressed performance. See # 119251.

It is not a pure revert because we also need to allow
`rustc::potential_query_instability` in one more place now because of
the revert.
@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jan 1, 2024
@Noratrieb
Copy link
Member

I don't think its worth bothering, the regression is tiny and only in extreme stress tests. Running the cachegrind command on a regression does reveal that the additional executed instructions are in rustc_lint and hashbrown so this isn't noise, but 🤷 I would just accept it

@cjgillot
Copy link
Contributor

cjgillot commented Jan 3, 2024

I agree with @Nilstrieb. The original PR was in some sense a bugfix, with a tiny regression.

@cjgillot cjgillot closed this Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants