Store hir_id_to_def_id in OwnerNodes.

[cjgillot]

Half step in #89278.

The HirId -> LocalDefId is currently untracked by incr. comp.
Although it has not been identified as causing incr. comp. bugs, there is no insurance against such future bugs.

This PR aims to restructure those maps consistently with the HIR itself.

[cjgillot]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit a8771c6800377125b7fc5df00b60563bb529c198 with merge beaf918adcf84a91683827db6b76fd8f00681595...

[bors]

☀️ Try build successful - checks-actions
Build commit: beaf918adcf84a91683827db6b76fd8f00681595 (beaf918adcf84a91683827db6b76fd8f00681595)

[rust-timer]

Queued beaf918adcf84a91683827db6b76fd8f00681595 with parent 49d4232, future comparison URL.

[rust-timer]

Finished benchmarking commit (beaf918adcf84a91683827db6b76fd8f00681595): comparison url.

Summary: This change led to large relevant regressions 😿 in compiler performance.

• Large regression in instruction counts (up to 2.9% on incr-unchanged builds of match-stress-enum)

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking 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 led to changes in compiler perf.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf +perf-regression

[cjgillot]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 1d9023ef83a39165a1d255517bf75025599b2730 with merge 89f519c544b7437eda1f1deb79c9784bc4b60f1a...

[bors]

☀️ Try build successful - checks-actions
Build commit: 89f519c544b7437eda1f1deb79c9784bc4b60f1a (89f519c544b7437eda1f1deb79c9784bc4b60f1a)

[rust-timer]

Queued 89f519c544b7437eda1f1deb79c9784bc4b60f1a with parent cafc458, future comparison URL.

[rust-timer]

Finished benchmarking commit (89f519c544b7437eda1f1deb79c9784bc4b60f1a): comparison url.

Summary: This change led to large relevant mixed results 🤷 in compiler performance.

• Small improvement in instruction counts (up to -0.4% on full builds of unused-warnings)
• Large regression in instruction counts (up to 3.0% on incr-unchanged builds of match-stress-enum)

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking 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 led to changes in compiler perf.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf +perf-regression

[bors]

☔ The latest upstream changes (presumably #93301) made this pull request unmergeable. Please resolve the merge conflicts.

[cjgillot]

Replaced by #93301.