Skip to content

remove constant evaluation hack in super_relate_consts #111622

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

BoxyUwU
Copy link
Member

@BoxyUwU BoxyUwU commented May 15, 2023

super_relate_consts has as hack in it to work around the fact that normalize_param_env_or_error is broken. When relating two constants we attempt to evaluate them (aka normalize them). This is not an issue in any way specific to const generics, type aliases also have the same issue as demonstrated in this code.

Opening just for a crater run

r? @compiler-errors

@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 May 15, 2023
@compiler-errors
Copy link
Member

@bors try

@bors
Copy link
Collaborator

bors commented May 15, 2023

⌛ Trying commit 8fbccd1f5dda000ceda7aca10e645f64bb1e5adc with merge b7d03861bf345e4ad2ddeaeb856c296223a4d00f...

@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented May 16, 2023

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

@compiler-errors
Copy link
Member

@craterbot check

@rust-timer build b7d03861bf345e4ad2ddeaeb856c296223a4d00f

@rust-timer

This comment has been minimized.

@craterbot
Copy link
Collaborator

👌 Experiment pr-111622 created and queued.
🤖 Automatically detected try build b7d03861bf345e4ad2ddeaeb856c296223a4d00f
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot craterbot added S-waiting-on-crater Status: Waiting on a crater run to be completed. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 16, 2023
@craterbot
Copy link
Collaborator

🚧 Experiment pr-111622 is now running

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (b7d03861bf345e4ad2ddeaeb856c296223a4d00f): comparison URL.

Overall result: ✅ improvements - no action needed

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 may lead to changes in compiler perf.

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

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
1.7% [1.7%, 1.7%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-1.5% [-1.5%, -1.5%] 6
All ❌✅ (primary) - - 0

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 644.092s -> 642.909s (-0.18%)

@craterbot
Copy link
Collaborator

🎉 Experiment pr-111622 is completed!
📊 6 regressed and 5 fixed (275257 total)
📰 Open the full report.

⚠️ If you notice any spurious failure please add them to the blacklist!
ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot craterbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-crater Status: Waiting on a crater run to be completed. labels May 16, 2023
@BoxyUwU BoxyUwU force-pushed the remove_eval_hack branch from 8fbccd1 to 61f0560 Compare May 17, 2023 18:06
@rust-log-analyzer

This comment has been minimized.

@BoxyUwU
Copy link
Member Author

BoxyUwU commented May 26, 2023

I think I would not like to land this all the regressions seem to be things that ought to work anyway and the motivation for this change is not that big since #111623 is also viable. Good to have the crater results though

@BoxyUwU BoxyUwU closed this May 26, 2023
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.

7 participants