summaryrefslogtreecommitdiff
path: root/lib/Target/ARM/ARMInstrNEON.td
diff options
context:
space:
mode:
authorTom Stellard <thomas.stellard@amd.com>2014-04-09 00:20:58 +0000
committerTom Stellard <thomas.stellard@amd.com>2014-04-09 00:20:58 +0000
commit886b940a1d6fedd28b84bd3fe06963bfd1451382 (patch)
tree55c37f75a489db57e3e2576365746fe29064ecc7 /lib/Target/ARM/ARMInstrNEON.td
parentcccd27683c7fa4a9e8e09d2f2a735a9bb6e56a0b (diff)
downloadllvm-886b940a1d6fedd28b84bd3fe06963bfd1451382.tar.gz
llvm-886b940a1d6fedd28b84bd3fe06963bfd1451382.tar.bz2
llvm-886b940a1d6fedd28b84bd3fe06963bfd1451382.tar.xz
Merging r204155:
------------------------------------------------------------------------ r204155 | wschmidt | 2014-03-18 10:32:50 -0400 (Tue, 18 Mar 2014) | 16 lines Fix PR19144: Incorrect offset generated for int-to-fp conversion at -O0. When converting a signed 32-bit integer to double-precision floating point on hardware without a lfiwax instruction, we have to instead use a lfd followed by fcfid. We were erroneously offsetting the address by 4 bytes in preparation for either a lfiwax or lfiwzx when generating the lfd. This fixes that silly error. This was not caught in the test suite since the conversion tests were run with -mcpu=pwr7, which implies availability of lfiwax. I've added another test case for older hardware that checks the code we expect in the absence of lfiwax and other flavors of fcfid. There are fewer tests in this test case because we punt to DAG selection in more cases on older hardware. (We must generate complex fiddly sequences in those cases, and there is marginal benefit in duplicating that logic in fast-isel.) ------------------------------------------------------------------------ git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_34@205824 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/Target/ARM/ARMInstrNEON.td')
0 files changed, 0 insertions, 0 deletions