summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorRichard Sandiford <rsandifo@linux.vnet.ibm.com>2013-08-23 11:18:53 +0000
committerRichard Sandiford <rsandifo@linux.vnet.ibm.com>2013-08-23 11:18:53 +0000
commita481f5854203e81cde5bba83e3f4c9a7c321fd29 (patch)
treec5813079ba99efebb52f072d1e4b20bbfdcc398e /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent37cd6cfba2e92fa89fbc4e8653edf1bb3229ba0d (diff)
downloadbcm5719-llvm-a481f5854203e81cde5bba83e3f4c9a7c321fd29.tar.gz
bcm5719-llvm-a481f5854203e81cde5bba83e3f4c9a7c321fd29.zip
[SystemZ] Prefer LHI;ST... over LAY;MV...
If we had a store of an integer to memory, and the integer and store size were suitable for a form of MV..., we used MV... no matter what. We could then have sequences like: lay %r2, 0(%r3,%r4) mvi 0(%r2), 4 In these cases it seems better to force the constant into a register and use a normal store: lhi %r2, 4 stc %r2, 0(%r3, %r4) since %r2 is more likely to be hoisted and is easier to rematerialize. llvm-svn: 189098
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud