diff options
| author | Craig Topper <craig.topper@intel.com> | 2018-02-14 18:53:29 +0000 |
|---|---|---|
| committer | Craig Topper <craig.topper@intel.com> | 2018-02-14 18:53:29 +0000 |
| commit | 6a09aab29418113bf9342598f18706b340021c0f (patch) | |
| tree | 3ee8f47d239705c3335127712f8490f51312159c /llvm/unittests/Bitcode/BitReaderTest.cpp | |
| parent | 5e52022af645661856f60e00f5e8dd9ee38863cd (diff) | |
| download | bcm5719-llvm-6a09aab29418113bf9342598f18706b340021c0f.tar.gz bcm5719-llvm-6a09aab29418113bf9342598f18706b340021c0f.zip | |
[RegisterClassInfo] Invalidate the register pressure set limit cache when reserved regs or callee saved regs change
Previously we only invalidated the pressure set limit cached when the TargetRegisterInfo pointer changes. But as reserved regs and callee saved regs are used as part of calculating the limits we should invalidate when those change too.
I encountered this when reverting a patch from the 6.0 branch. One of the x86 test files had a function that used rbp as a frame pointer, making it reserved. It was followed by another function which didn't use rbp but had the same TRI so the pressure set limit cache was not invalidated. If i removed the function that used rbp as a frame pointer from the file, the remaining function then got a different register pressure limit for the GR16 pressure set. This caused the machine scheduler to change the scheduling for the function. This was an unexpected change from just deleting a function.
I don't have a test case for trunk because the particular x86 test case is different enough from the 6.0 branch to not be affected now.
Differential Revision: https://reviews.llvm.org/D43274
llvm-svn: 325153
Diffstat (limited to 'llvm/unittests/Bitcode/BitReaderTest.cpp')
0 files changed, 0 insertions, 0 deletions
