Home
last modified time | relevance | path

Searched full:corresponding (Results 1 – 25 of 128) sorted by relevance

123456

/arkcompiler/ets_runtime/ecmascript/
Dwaiter_list.h47 // the memory address data corresponding to the offset
70 …// When calling addnode If there is no corresponding memory data, add the node corresponding to th…
/arkcompiler/runtime_core/runtime/bridge/arch/arm/
Dinterpreter_to_compiled_code_bridge_dyn_arm.S63 // to the corresponding handler.
66 // Handlers are distinguished by format and located in the corresponding files with name:
69 // new call format was introduced and you have to implement the corresponding handler.
Dinterpreter_to_compiled_code_bridge_armhf.S68 // It takes an argument in arg_reg and stores it to the corresponding stack space
70 // After the arg gets storeg the macro advances the corresponding pointer
359 // to the corresponding handler.
362 // Handlers are distinguished by format and located in the corresponding files with name:
365 // new call format was introduced and you have to implement the corresponding handler.
Dinterpreter_to_compiled_code_bridge_arm.S200 // to the corresponding handler.
203 // Handlers are distinguished by format and located in the corresponding files with name:
206 // new call format was introduced and you have to implement the corresponding handler.
/arkcompiler/runtime_core/docs/
Dfile_format.md39 Local entities has the same header as the corresponding foreign. So
265 …claring class in a [`ClassRegionIndex`](#classregionindex) structure. Corresponding index entry mu…
266 … field's type in a [`ClassRegionIndex`](#classregionindex) structure. Corresponding index entry mu…
279 …claring class in a [`ClassRegionIndex`](#classregionindex) structure. Corresponding index entry mu…
280 … field's type in a [`ClassRegionIndex`](#classregionindex) structure. Corresponding index entry mu…
333 …claring class in a [`ClassRegionIndex`](#classregionindex) structure. Corresponding index entry mu…
334 …d's prototype in a [`ProtoRegionIndex`](#classregionindex) structure. Corresponding index entry mu…
348 …claring class in a [`ClassRegionIndex`](#classregionindex) structure. Corresponding index entry mu…
349 …d's prototype in a [`ProtoRegionIndex`](#classregionindex) structure. Corresponding index entry mu…
431 …imitive types. For each non-primitive type in the shorty there is the corresponding element in the…
[all …]
/arkcompiler/runtime_core/runtime/mem/gc/
Dbitmap.h100 …* \brief Atomically clear bit corresponding to addr. If the bit is set, clear it atomically. Other…
107 * \brief Atomically test bit corresponding to addr.
443 * \brief Set bit corresponding to addr.
453 * \brief Clear bit corresponding to addr.
463 * \brief Clear bits corresponding to addr range [begin, end).
472 * \brief Test bit corresponding to addr.
482 * \brief Test bit corresponding to addr if addr is valid.
494 …* \brief Atomically set bit corresponding to addr. If the bit is not set, set it atomically. Other…
505 …* \brief Atomically clear bit corresponding to addr. If the bit is set, clear it atomically. Other…
516 * \brief Atomically test bit corresponding to addr.
Dgc_extension_data.h46 // language extension got the corresponding type of data
/arkcompiler/ets_runtime/ecmascript/tests/
Dlayout_info_test.cpp116 EXPECT_EQ(result, 1); // 1: Index corresponding to key1 in HWTEST_F_L0()
128 EXPECT_EQ(result, 4); // 4: Index corresponding to key4 in HWTEST_F_L0()
130 EXPECT_EQ(result, 10); // 10: Index corresponding to key10 in HWTEST_F_L0()
132 EXPECT_EQ(result, 5); // 5: Index corresponding to key5 in HWTEST_F_L0()
/arkcompiler/runtime_core/runtime/
Dmonitor.h108 * @param obj an object header of corresponding object
126 * @param obj an object header of corresponding object
140 * @param obj an object header of corresponding object
/arkcompiler/runtime_core/runtime/bridge/arch/aarch64/
Dinterpreter_to_compiled_code_bridge_dyn_aarch64.S70 // to the corresponding handler.
73 // Handlers are distinguished by format and located in the corresponding files with name:
76 // new call format was introduced and you have to implement the corresponding handler.
Dinterpreter_to_compiled_code_bridge_aarch64.S38 // It takes a pair (argument, type tag) and stores to the corresponding stack space
40 // After the arg gets storeg the macro advances the corresponding pointer
247 // to the corresponding handler.
250 // Handlers are distinguished by format and located in the corresponding files with name:
253 // new call format was introduced and you have to implement the corresponding handler.
/arkcompiler/runtime_core/runtime/bridge/arch/amd64/
Dinterpreter_to_compiled_code_bridge_dyn_amd64.S82 // to the corresponding handler.
85 // Handlers are distinguished by format and located in the corresponding files with name:
88 // new call format was introduced and you have to implement the corresponding handler.
Dinterpreter_to_compiled_code_bridge_amd64.S100 // It takes an argument in arg_reg and stores it to the corresponding stack space
102 // After the arg gets stored the macro advances the corresponding pointer
350 // to the corresponding handler.
353 // Handlers are distinguished by format and located in the corresponding files with name:
356 // new call format was introduced and you have to implement the corresponding handler.
/arkcompiler/runtime_core/compiler/docs/
Dif_conversion_doc.md59 6. The number of Phi instruction in `PBB`, which have different inputs from corresponding predecess…
70 … also removed, but input from `BB`(`JBB 2` for Diamond) is changed to corresponding Select instruc…
/arkcompiler/runtime_core/docs/diagrams/
Dgc-mark.puactivity27 :Put the object into the corresponding queue;
Dstacktrace.pusequence25 StackPrinter -> StackPrinter: For each address, find the corresponding VMA and determine the librar…
/arkcompiler/runtime_core/runtime/mem/
Dalloc_config.h104 * \brief Initialize a Crossing map for the corresponding memory ranges.
114 * \brief Remove a Crossing map for the corresponding memory ranges.
318 * \brief Initialize a Crossing map for the corresponding memory ranges.
328 * \brief Remove a Crossing map for the corresponding memory ranges.
/arkcompiler/runtime_core/scripts/
Drun-clang-format17 # look like and output corresponding diff. Exit with the same code as diff.
/arkcompiler/runtime_core/tests/verifier-tests/
Dbug_2088.pa34 …n error when the field resolves to a field with size or type that is not corresponding to bytecode
/arkcompiler/ets_runtime/ecmascript/builtins/
Dbuiltins_locale.cpp170 // 4. Return the substring of locale corresponding to the unicode_language_id production. in GetBaseName()
292 …// 5. Return the substring of locale corresponding to the unicode_language_subtag production of the in GetLanguage()
320 … // 6. Return the substring of locale corresponding to the unicode_script_subtag production of the in GetScript()
349 … // 6. Return the substring of locale corresponding to the unicode_region_subtag production of the in GetRegion()
/arkcompiler/runtime_core/compiler/optimizer/optimizations/
Dtypes_resolving.h31 …* In case of success, the corresponding types are put in AnyType heck, which are the inputs of the…
/arkcompiler/runtime_core/cmake/
DREADME.md43 For example, to check style issues in the opt.cpp file, you can use corresponding clang-format targ…
/arkcompiler/runtime_core/docs/bc_verification/
Dtype_system.md27 - `~` invariant, means that corresponding parameter in subtyping relation must be in subtype and su…
/arkcompiler/runtime_core/tests/cts-generator/cts-template/
Dstobj.v.yaml477 that is not corresponding to bytecode in PandaAssembly context.
512 …eports error when the field resolves to a field with size that is not corresponding to bytecode in…
550 …k that verifier does not report any error when the field has size or type corresponding to bytecode
591 …verifier reports error when the register contains a value of type not corresponding to the bytecod…
674 a value of type not corresponding to the bytecode in PandaAssembly context.
/arkcompiler/runtime_core/runtime/bridge/arch/x86/
Dinterpreter_to_compiled_code_bridge_x86.S199 // to the corresponding handler.
202 // Handlers are distinguished by format and located in the corresponding files with name:
205 // new call format was introduced and you have to implement the corresponding handler.

123456