aboutsummaryrefslogtreecommitdiff
path: root/lldb/scripts/Python/python-wrapper.swig
diff options
context:
space:
mode:
authorRichard Sandiford <rsandifo@linux.vnet.ibm.com>2013-09-25 10:11:07 +0000
committerRichard Sandiford <rsandifo@linux.vnet.ibm.com>2013-09-25 10:11:07 +0000
commit35ec4e356c6bbe5b6628ae27e9ce6806fbc59bda (patch)
tree6c4b05ee53e45463f584200b19f7ad47e32cd573 /lldb/scripts/Python/python-wrapper.swig
parent1ccd2f2aee3705deacb381e16415e13ec8f47bae (diff)
downloadllvm-35ec4e356c6bbe5b6628ae27e9ce6806fbc59bda.zip
llvm-35ec4e356c6bbe5b6628ae27e9ce6806fbc59bda.tar.gz
llvm-35ec4e356c6bbe5b6628ae27e9ce6806fbc59bda.tar.bz2
[SystemZ] Add instruction-shortening pass
When loading immediates into a GR32, the port prefered LHI, followed by LLILH or LLILL, followed by IILF. LHI and IILF are natural 32-bit operations, but LLILH and LLILL also clear the upper 32 bits of the register. This was represented as taking a 32-bit subreg of a 64-bit assignment. Using subregs for something as simple as a move immediate was probably a bad idea. Also, I have patches to add support for the high-word facility, and we don't want something like LLILH and LLILL to stop the high word of the same GPR from being used. This patch therefore uses LHI and IILF to begin with and adds a late machine-specific pass to use LLILH and LLILL if the other half of the register is not live. The high-word patches extend this behavior to IIHF, LLIHL and LLIHH. No behavioral change intended. llvm-svn: 191363
Diffstat (limited to 'lldb/scripts/Python/python-wrapper.swig')
0 files changed, 0 insertions, 0 deletions