Home
last modified time | relevance | path

Searched refs:CMN (Results 1 – 12 of 12) sorted by relevance

/external/sonivox/arm-hybrid-22k/lib_src/
DARM-E_mastergain_gnu.s81 CMN r4, r6 @check for negative saturation
90 CMN r5, r6 @check for negative saturation
/external/sonivox/arm-wt-22k/lib_src/
DARM-E_mastergain_gnu.s81 CMN r4, r6 @check for negative saturation
90 CMN r5, r6 @check for negative saturation
/external/v8/src/arm/
Dconstants-arm.h203 CMN = 11 << 21, // Compare Negated. enumerator
Ddisasm-arm.cc873 case CMN: { in DecodeType01()
Dsimulator-arm.cc2276 case CMN: { in DecodeType01()
Dassembler-arm.cc1143 addrmod1(cond | CMN | S, src1, r0, src2); in cmn()
/external/webkit/Source/JavaScriptCore/assembler/
DARMAssembler.h136 CMN = (0xb << 21), enumerator
378 emitInst(static_cast<ARMWord>(cc) | CMN | SET_CC, 0, rn, op2);
/external/llvm/lib/Target/ARM/
DREADME.txt587 The CMN instruction sets the flags like an ADD instruction, while CMP sets
588 them like a subtract. Therefore to be able to use CMN for comparisons other
DARMInstrInfo.td3180 // FIXME: We have to be careful when using the CMN instruction and comparison
3197 // However, the CMN gives the *opposite* result when r1 is 0. This is because
3198 // the carry flag is set in the CMP case but not in the CMN case. In short, the
3202 // when r0 >= 0). The CMN instruction doesn't perform a NOT of 0 so there is
3213 // Therefore, we should disable CMN when comparing against zero, until we can
3214 // limit when the CMN instruction is used (when we know that the RHS is not 0 or
3221 //defm CMN : AI1_cmp_irs<0b1011, "cmn",
DARMInstrThumb.td929 // CMN register
931 //FIXME: Disable CMN, as CCodes are backwards from compare expectations
DARMInstrThumb2.td2685 //FIXME: Disable CMN, as CCodes are backwards from compare expectations
/external/llvm/test/MC/ARM/
Dbasic-arm-instructions.s394 @ CMN