Skip to content

Only emit gep not gepi #120483

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
Closed

Conversation

saethlin
Copy link
Member

r? @ghost

A handful of people were speculating about the perf impact of gep vs gepi so let's see what this does....

@saethlin saethlin added the S-experimental Status: Ongoing experiment that does not require reviewing and won't be merged in its current state. label Jan 30, 2024
@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 30, 2024
@saethlin saethlin removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jan 30, 2024
@saethlin
Copy link
Member Author

@bors try @rust-timer queue

@rust-timer

This comment has been minimized.

@rustbot rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Jan 30, 2024
@bors
Copy link
Collaborator

bors commented Jan 30, 2024

⌛ Trying commit 2ca30e9 with merge c795a6f...

bors added a commit to rust-lang-ci/rust that referenced this pull request Jan 30, 2024
Only emit gep not gepi

r? `@ghost`

A handful of people were speculating about the perf impact of `gep` vs `gepi` so let's see what this does....
@bors
Copy link
Collaborator

bors commented Jan 30, 2024

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

@rust-timer

This comment has been minimized.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (c795a6f): comparison URL.

Overall result: ❌ regressions - 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.

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-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)
2.7% [0.7%, 6.5%] 236
Regressions ❌
(secondary)
2.8% [0.5%, 9.0%] 227
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 2.7% [0.7%, 6.5%] 236

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
2.1% [2.1%, 2.1%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-4.3% [-4.3%, -4.3%] 1
Improvements ✅
(secondary)
-1.0% [-1.0%, -1.0%] 1
All ❌✅ (primary) -1.1% [-4.3%, 2.1%] 2

Cycles

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
1.7% [0.7%, 4.0%] 70
Regressions ❌
(secondary)
6.1% [1.1%, 17.8%] 22
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 1.7% [0.7%, 4.0%] 70

Binary size

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
0.3% [0.1%, 1.0%] 25
Regressions ❌
(secondary)
1.0% [0.3%, 1.3%] 39
Improvements ✅
(primary)
-0.1% [-0.1%, -0.1%] 3
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.2% [-0.1%, 1.0%] 28

Bootstrap: 661.382s -> 675.337s (2.11%)
Artifact size: 308.09 MiB -> 308.13 MiB (0.01%)

@rustbot rustbot added perf-regression Performance regression. and removed S-waiting-on-perf Status: Waiting on a perf run to be completed. labels Jan 30, 2024
@Kobzol
Copy link
Contributor

Kobzol commented Jan 30, 2024

Interesting, looks like some nice wins on runtime hashmap benchmarks 🤔
image

@saethlin
Copy link
Member Author

Yeah. I'll look into that later, but for now I have my answer.

@saethlin saethlin closed this Jan 30, 2024
@saethlin saethlin deleted the no-inbounds branch January 30, 2024 11:58
bors added a commit to rust-lang-ci/rust that referenced this pull request Feb 14, 2024
[perf experiment] Only emit gep not gepi

r? `@ghost`

Re-creating rust-lang#120483, trying to measure the perf impact of `gep` vs `gepi`. That previous PR was with LLVM 17 and it found a runtime perf _improvement_, so in part this PR is assessing if that was fixed in LLVM 18.

Codegen tests will fail.
bors added a commit to rust-lang-ci/rust that referenced this pull request May 12, 2024
[perf experiment] Only emit gep not gepi

r? `@ghost`

Re-creating rust-lang#120483, trying to measure the perf impact of `gep` vs `gepi`. That previous PR was with LLVM 17 and it found a runtime perf _improvement_, so in part this PR is assessing if that was fixed in LLVM 18.

Codegen tests will fail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
perf-regression Performance regression. S-experimental Status: Ongoing experiment that does not require reviewing and won't be merged in its current state. 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.

5 participants