Remove eval_always for privacy_access_levels.

[cjgillot]

r? @Aaron1011

[cjgillot]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 76acc6aed7f6c191fb79fa8824d1c622fcba0e77 with merge 956e8e72f5863bf517d5b48ff06982077631673b...

[bors]

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

[rust-timer]

Queued 956e8e72f5863bf517d5b48ff06982077631673b with parent 5fd3a5c, future comparison URL.

[rust-timer]

Finished benchmarking commit (956e8e72f5863bf517d5b48ff06982077631673b): comparison url.

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

• Moderate regression in instruction counts (up to 0.7% on incr-full builds of deeply-nested-async)

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