summaryrefslogtreecommitdiffstats
path: root/llvm/test/CodeGen/SystemZ/Large/spill-01.py
Commit message (Collapse)AuthorAgeFilesLines
* Python compat - print statementSerge Guelton2019-01-031-12/+15
| | | | | | | | | Make sure all print statements are compatible with Python 2 and Python3 using the `from __future__ import print_function` statement. Differential Revision: https://reviews.llvm.org/D56249 llvm-svn: 350307
* Update SystemZ/Large test generators to handle new gep IR syntaxDavid Blaikie2015-02-271-1/+1
| | | | llvm-svn: 230810
* Update SystemZ/Large test generators to handle new load IR syntaxDavid Blaikie2015-02-271-1/+1
| | | | llvm-svn: 230809
* [SystemZ] Use MVC to spill loads and storesRichard Sandiford2013-07-021-0/+40
Try to use MVC when spilling the destination of a simple load or the source of a simple store. As explained in the comment, this doesn't yet handle the case where the load or store location is also a frame index, since that could lead to two simultaneous scavenger spills, something the backend can't handle yet. spill-02.py tests that this restriction kicks in, but unfortunately I've not yet found a case that would fail without it. The volatile trick I used for other scavenger tests doesn't work here because we can't use MVC for volatile accesses anyway. I'm planning on relaxing the restriction later, hopefully with a test that does trigger the problem... Tests @f8 and @f9 also showed that L(G)RL and ST(G)RL were wrongly classified as SimpleBDX{Load,Store}. It wouldn't be easy to test for that bug separately, which is why I didn't split out the fix as a separate patch. llvm-svn: 185434
OpenPOWER on IntegriCloud