@WG-prioritization/alerts #58368 has been nominated for discussion in T-compiler
meeting.
cc @LeSeulArtichaut thoughts?
Hmm... this is tricky because it's been so long that the perf.rlo data isn't available any more.
is there a way we can re-perf it?
Wesley Wiser said:
Hmm... this is tricky because it's been so long that the perf.rlo data isn't available any more.
yeah, so ... can we maybe run benchmarks with current master code and then run again with master + that identified commit reverted?
Should we do perf runs by reverting potential culprits?
I have no idea if would be as easy as reverting that commit, let's pretend I have said "revert" between quotes :), I meant, chaging the code to what it looked like before and with it working on current master
DPC said:
is there a way we can re-perf it?
I guess in the way I've said, wouldn't be a correct thing to run perf with master and compare that run with the old code because there are a lot of unrelated improvements since then and we would be comparing non sense stuff
anyway, when I've said thoughts, what I meant was if nomination bullets were more or less correct and summarizes the issue correctly :)
I mean basically what you said at the same time
LeSeulArtichaut said:
Should we do perf runs by reverting potential culprits?
yep that's what is done sometimes in such cases
Yeah, I think that's the best we can do. I just hope reverting that commit isn't too messy.
#58368's nomination has been removed.