Searched full:operation (Results 1 – 25 of 250) sorted by relevance
12345678910
| /arkcompiler/runtime_core/assembler/tests/ |
| D | lexer_test.cpp | 30 ASSERT_EQ(TokenTypeWhat(tok.first[0].type), "OPERATION") << "OPERATION expected"; in TEST()
42 ASSERT_EQ(TokenTypeWhat(tok.first[0].type), "OPERATION") << "OPERATION expected"; in TEST()
52 ASSERT_EQ(TokenTypeWhat(tok.first[0].type), "OPERATION") << "OPERATION expected"; in TEST()
53 ASSERT_EQ(TokenTypeWhat(tok.first[1].type), "OPERATION") << "OPERATION expected"; in TEST()
56 ASSERT_EQ(TokenTypeWhat(tok.first[4].type), "OPERATION") << "OPERATION expected"; in TEST()
66 ASSERT_EQ(TokenTypeWhat(tok.first[0].type), "OPERATION") << "OPERATION expected"; in TEST()
76 ASSERT_EQ(TokenTypeWhat(tok.first[0].type), "OPERATION") << "OPERATION expected"; in TEST()
88 ASSERT_EQ(TokenTypeWhat(tok.first[0].type), "OPERATION") << "OPERATION expected"; in TEST()
|
| /arkcompiler/ets_frontend/es2panda/test/parser/js/ |
| D | invalid-left-hand-side-in-prefix-operation-expected.txt | 1 SyntaxError: Invalid left-hand side in prefix operation [invalid-left-hand-side-in-prefix-operation…
|
| /arkcompiler/runtime_core/docs/ |
| D | rationale-for-bytecode.md | 14 somewhere in memory and executes corresponding _operations_ on operation's arguments,
15 also known as operation's _operands_. Operands may be _registers_ (very fast "variables" located
45 One very important question is how an operation refers to its operands.
47 In _stack-based_ approach, operands are implicitly encoded in the operation, which results in
60 In _register-based approach_, operands are explicitly encoded in the operation, which results in
153 | operation code | vreg 1 | vreg 2 |
162 | operation code | vreg 1 | vreg 2 |
187 One option is to make the operation _statically typed_, i.e. specify explicitly that it works only
191 Another option is to make the operation _dynamically typed_, i.e. specify that `adda ...` handles
|
| /arkcompiler/runtime_core/tests/cts-generator/cts-template/ |
| D | nop.yaml | 18 title: No operation
19 description: Perform an operation without behavior.
|
| /arkcompiler/runtime_core/scripts/ |
| D | run_check_atomic_format.py | 111 "specified for atomic operation".format(FILE, index))
116 "atomic operation".format(FILE, index))
|
| /arkcompiler/runtime_core/tests/cts-assembly/ |
| D | math-43.pa | 14 #Assert that operation divu works fine
|
| D | op-04.pa | 14 #Assert that operation jmp works fine
|
| D | obj-03.pa | 14 #Assert that operation newobj works fine
|
| D | op-08.pa | 14 #Assert that operation jgtz works fine
|
| D | op-09.pa | 14 #Assert that operation jlez works fine
|
| D | op-10.pa | 14 #Assert that operation jgez works fine
|
| D | op-05.pa | 14 #Assert that operation jeqz works fine
|
| D | op-14.pa | 14 #Assert that operation jgt works fine
|
| D | op-26.pa | 14 #Assert that operation u32toi64 works fine
|
| D | op-20.pa | 14 #Assert that operation lda.str works fine
|
| D | op-06.pa | 14 #Assert that operation jnez works fine
|
| D | math-45.pa | 14 #Assert that operation modu2 works fine
|
| D | op-07.pa | 14 #Assert that operation jltz works fine
|
| D | op-03.pa | 14 #Assert that operation sta.64 works fine
|
| D | op-11.pa | 14 #Assert that operation jeq works fine
|
| D | math-18.pa | 14 # assert(151 ashr 1 == 75) operation --> ashr
|
| D | math-36.pa | 14 # assert(neg(1) == -1) operation --> neg.64
|
| D | math-03.pa | 14 # assert(2 * 3 == 6) operation --> muli
|
| D | obj-04.pa | 14 #Assert that operation initobj works fine
|
| /arkcompiler/runtime_core/verification/models/ |
| D | README.md | 4 And compatibility check operation is changed to:
|
12345678910