summaryrefslogtreecommitdiffstats
path: root/llvm/test/MC/ARM/fp-const-errors.s
Commit message (Collapse)AuthorAgeFilesLines
* ARM: fix vmov.i64 immediate validity checkTim Northover2016-07-141-0/+3
| | | | | | Typo meant we were only checking the low byte (repeatedly). llvm-svn: 275437
* Add ARM fconsts/fconstd aliases for vmov.f32/vmov.f64David Peixotto2014-01-071-0/+22
This commit adds the pre-UAL aliases of fconsts and fconstd for vmov.f32 and vmov.f64. They use an InstAlias rather than a MnemonicAlias to properly support the predicate operand. We need to support encoded 8-bit constants in order to implement the pre-UAL fconsts/fconstd aliases for vmov.f32/vmov.f64, so this commit also fixes parsing of encoded floating point constants used in vmov.f32/vmov.f64 instructions. Now we can support assembly code like this: fconsts s0, #0x70 which is equivalent to vmov.f32 s0, #1.0. Most of the code was already in place to support this feature. Previously the code was trying to accept encoded 8-bit float constants for the vmov.f32/vmov.f64 instructions. It looks like the support for parsing encoded floats was lost in a refactoring in commit r148556 and we did not have any tests in place to catch it. The change in this commit is to keep the parsed value as a 32-bit float instead of a 64-bit double because that is what the isFPImm() function expects to find. There is no loss of precision by using a 32-bit float here because we are still limited to an 8-bit encoded value in the end. Additionally, we explicitly reject encoded 8-bit floats for vmovf.32/64. This is the same as the current behavior, but we now do it explicitly rather than accidently. llvm-svn: 198697
OpenPOWER on IntegriCloud