[experiment] remove attributes from Terminator - #161167
Conversation
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
[experiment] remove attributes from Terminator
|
The job Click to see the possible cause of the failure (guessed by this bot) |
This comment has been minimized.
This comment has been minimized.
|
By the way the only attribute that (currently) has meaning here is the pub struct Terminator<'tcx> {
pub source_info: SourceInfo,
pub kind: TerminatorKind<'tcx>,
- pub attributes: ThinVec<AttributeKind>,
+ pub unroll: UnrollAttr,
} |
|
Finished benchmarking commit (41edbdc): comparison URL. Overall result: ❌ regressions - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @rustbot label: -S-waiting-on-perf -perf-regression 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 -3.8%, secondary 0.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 3.5%, secondary -3.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.2%, secondary -0.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 459.382s -> 456.498s (-0.63%) |
That probably wouldn't help much, because Unroll has Anyway, contraray to the original analysis, looks like this list is actually not the cause of the regression in #156816, or something significant changed in the meantime that changes it. I'll create a new issue and write down what I've found. |
I'm getting a lot of mixed signals from it, so I want to get some baseline measurement to see the true cost.