en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/ARM/fp-const-errors.s#e093bad4 [ARM] Use new assembler diags for ARMThis converts the ARM AsmParser to use the new assembly matcher errorreporting mechanism, which allows errors to be reported for multipleinstruction encodings when it is ambiguous which one the user intendedto use.By itself this doesn't improve many error messages, because we don't havediagnostic text for most operand types, but as we add that then this will allowmore of those diagnostic strings to be used when they are relevant.Differential revision: https://reviews.llvm.org/D31530llvm-svn: 314779 List of files: /llvm-project-15.0.7/llvm/test/MC/ARM/fp-const-errors.s Tue, 03 Oct 2017 10:26:11 +0000 Oliver Stannard <oliver.stannard@arm.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/ARM/fp-const-errors.s#6003fb58 ARM: fix vmov.i64 immediate validity checkTypo meant we were only checking the low byte (repeatedly).llvm-svn: 275437 List of files: /llvm-project-15.0.7/llvm/test/MC/ARM/fp-const-errors.s Thu, 14 Jul 2016 17:04:34 +0000 Tim Northover <tnorthover@apple.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/ARM/fp-const-errors.s#a872e0e0 Add ARM fconsts/fconstd aliases for vmov.f32/vmov.f64This commit adds the pre-UAL aliases of fconsts and fconstd forvmov.f32 and vmov.f64. They use an InstAlias rather than aMnemonicAlias to properly support the predicate operand.We need to support encoded 8-bit constants in order to implement thepre-UAL fconsts/fconstd aliases for vmov.f32/vmov.f64, so thiscommit also fixes parsing of encoded floating point constants usedin vmov.f32/vmov.f64 instructions. Now we can support assembly codelike this: fconsts s0, #0x70which 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 floatconstants for the vmov.f32/vmov.f64 instructions. It looks like thesupport for parsing encoded floats was lost in a refactoring incommit 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-bitfloat instead of a 64-bit double because that is what the isFPImm()function expects to find. There is no loss of precision by using a32-bit float here because we are still limited to an 8-bit encodedvalue in the end.Additionally, we explicitly reject encoded 8-bit floats forvmovf.32/64. This is the same as the current behavior, but we now doit explicitly rather than accidently.llvm-svn: 198697 List of files: /llvm-project-15.0.7/llvm/test/MC/ARM/fp-const-errors.s Tue, 07 Jan 2014 18:19:23 +0000 David Peixotto <dpeixott@codeaurora.org>