summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py
diff options
context:
space:
mode:
authorTobias Grosser <tobias@grosser.es>2016-02-01 10:07:43 +0000
committerTobias Grosser <tobias@grosser.es>2016-02-01 10:07:43 +0000
commitccbe383594fc3048bc4f6a7bc2e77c949862927f (patch)
tree06778caf06417433aa993e4cb5587e31450e666b /lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py
parent56b039ea1725d388620172c0512e015cb59383da (diff)
downloadbcm5719-llvm-ccbe383594fc3048bc4f6a7bc2e77c949862927f.tar.gz
bcm5719-llvm-ccbe383594fc3048bc4f6a7bc2e77c949862927f.zip
ScopInfo: Drop dead code in schedule description
In https://llvm.org/svn/llvm-project/polly/trunk@251870 code was committed to avoid a failure in the presence of infinite loops, but the test case committed along with this change passes without the actual change. I looked back into the code and also checked with the original committer (Johannes), but could not find the reason why the code is needed. The introduction of LoopStacks for buildSchedule in one of the next commits will make it even more clear that this code is not needed, but I remove this ahead of time to facilitate bisecting in case I missed something. llvm-svn: 259347
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud