Reduce AttributeKind from 40 to 32 bytes#155788
Conversation
This comment has been minimized.
This comment has been minimized.
Reduce AttributeKind from 40 to 32 bytes
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
Fyi I tried this a while ago both with size 24 and 32, and both were perf regressions, which really surprised me. |
|
See #151507 |
|
Hmm your diff is a lot smaller so this might have some potential |
|
I have another commit lined up that does it without boxing anything, by removing deprecated's Span. The only user facing place where we need its span is in check_attr, where it lints for We should probably do a pass and see which spans are actually still used. They won't matter for AttributeKind's size though. |
|
@rust-timer build 7f7461f It doesn't listen to pr descriptions :) |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (7f7461f): comparison URL. Overall result: ❌ regressions - please read:Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. Next, please: If you can, justify the regressions found in this try perf run in writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -0.6%, secondary 1.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 6.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (secondary 0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 487.131s -> 488.874s (0.36%) |
@bors try @rust-timer queue