[llvm-dev] Machine Scheduler on Power PC: Latency Limit and Register Pressure
Stefan Pintilie via llvm-dev
llvm-dev at lists.llvm.org
Mon Oct 16 06:28:07 PDT 2017
Hi Andrew,
Actually, my main concern was the spill. My original text was probably not
very clear. Sorry about the confusion.
What I wanted to point out was exactly what Matthias mentioned in his
first email. The Pending queue is not considered in tryCandidate() and so
we can end up with a large number of similar instructions that
significantly increase register pressure. In my example it was loads. The
scheduler will take all the loads and schedule them together because they
all have the same latency and so are all in the Available queue. I agree
that in theory that is a good idea however in our case each load uses up
another register and we can technically end up with more consecutive loads
than total available physical registers. If we considered register
pressure we would start by putting all the loads together but then after a
few loads we would be forced to use a div to release some of the register
pressure.
Having said that, I tried your suggestion of setting
MicroOpBufferSize=1
and it certainly seems to improve things. (At least for the example I was
looking at.) Thank you for mentioning it.
I'll run a few more tests with that parameter change and hopefully that
will be enough to get what we want.
Matthias, Andrew, thank you both for the help.
Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171016/8de198d3/attachment.html>
More information about the llvm-dev
mailing list