Searched full:based (Results 1 – 25 of 349) sorted by relevance
12345678910>>...14
| /arkcompiler/runtime_core/static_core/docs/ |
| D | rationale-for-bytecode.md | 60 In _register-based approach_, operands are explicitly encoded in the operation, which results in
71 This example demonstrates a fundamental difference between two approaches. Stack-based approach
73 can be represented with a single byte, while register-based `add reg_dst, reg_src1, reg_src2` may
76 At the same time, to execute a stack-based addition we need to run 3 instructions compared to
77 just a single register-based instruction. Since the interpreter has an extra work to do to read
79 more _dispatch overhead_. Which means that the stack-based bytecode is slower by nature.
81 According to our experiment, uncompressed register-based bytecode can be reduced by ~26%
82 if substituted by a stack-based analogue. At the same time, performance becomes 10%-40% worse
87 **Panda uses register-based instruction set architecture**.
95 ~20% compared to pure register-based bytecode.
[all …]
|
| D | task_manager.md | 25 …kManager` for new tasks. TaskManager creates array of tasks in proportion based on the current con…
27 …based on some state of the system. The state of the system is provided by changing priority for Ta…
|
| D | cross-values.md | 24 * Regeneration is triggered automatically based on build dependencies;
131 …sm_defines` target being built (see [CMake-schematic](#schematic-of-cmake-based-build)). These sub…
133 #### Schematic of CMake-based build:
163 …d there are no any of `"auxiliary_binary_dirs"` (see [GN-schematic](#schematic-of-gn-based-build)).
164 #### Schematic of GN-based build:
182 …the toolchain. To detect such situation, a `CRC-32` checksum is generated based on '`.h`'-files wi…
186 …om the root `libasm_defines.S`, see [CMake-schematic](#schematic-of-cmake-based-build)) and `cross…
|
| /arkcompiler/runtime_core/docs/ |
| D | rationale-for-bytecode.md | 60 In _register-based approach_, operands are explicitly encoded in the operation, which results in
71 This example demonstrates a fundamental difference between two approaches. Stack-based approach
73 can be represented with a single byte, while register-based `add reg_dst, reg_src1, reg_src2` may
76 At the same time, to execute a stack-based addition we need to run 3 instructions compared to
77 just a single register-based instruction. Since the interpreter has an extra work to do to read
79 more _dispatch overhead_. Which means that the stack-based bytecode is slower by nature.
81 According to our experiment, uncompressed register-based bytecode can be reduced by ~26%
82 if substituted by a stack-based analogue. At the same time, performance becomes 10%-40% worse
87 **Panda uses register-based instruction set architecture**.
95 ~20% compared to pure register-based bytecode.
[all …]
|
| /arkcompiler/ets_frontend/ets2panda/test/parser/ets/import_tests/ |
| D | import_all.ets | 19 let x = all.foo(all.dbl /* double based signature */);
20 let y = all.foo(all.flt /* float based signature */);
21 let z = sub.foo("foo" /* string based signature */);
|
| D | import_name_1.ets | 18 let x = foo(dbl /* double based signature */);
19 let y = foo(flt /* float based signature */)
|
| D | import_relative_path.ets | 18 let x = all.foo(all.dbl /* double based signature */);
19 let y = all.foo(all.flt /* float based signature */);
|
| D | import_name_alias_1.ets | 18 let x = Foo(dbl /* double based signature */);
19 let y = Foo(flt /* float based signature */);
|
| D | import_all_alias_1.ets | 18 let x = Test.foo(Test.dbl /* double based signature */);
19 let y = Test.foo(Test.flt /* float based signature */);
|
| D | import_several_7.ets | 20 let x = Foo(dbl /* double based signature */);
21 let y = FOO(flt /* float based signature */);
|
| D | import_several_1.ets | 20 let x = foo(dbl /* double based signature */);
21 let y = foo(flt /* float based signature */);
|
| D | import_several_4.ets | 19 let x = foo(Test.dbl /* double based signature */);
20 let y = Test.foo(Test.flt /* float based signature */);
|
| D | import_several_6.ets | 19 let x = Foo(Test.dbl /* double based signature */);
20 let y = Test.foo(Test.flt /* float based signature */);
|
| D | import_several_3.ets | 19 let x = foo(all.dbl /* double based signature */);
20 let y = foo(all.flt /* float based signature */);
|
| D | import_several_5.ets | 19 let x = Foo(all.dbl /* double based signature */);
20 let y = Foo(all.flt /* float based signature */);
|
| /arkcompiler/runtime_core/isa/ |
| D | ChangeLog.md | 4 + Removed builtins and API for template-based generation for builtins
10 + Removed compatibility check based on the isa checksum.
|
| /arkcompiler/runtime_core/static_core/isa/ |
| D | ChangeLog.md | 12 + Removed builtins and API for template-based generation for builtins
18 + Removed compatibility check based on the isa checksum.
|
| /arkcompiler/runtime_core/taihe/compiler/taihe/utils/ |
| D | sources.py | 49 """Represents a file-based source code."""
71 """Represents a string-based source code."""
108 """Represents a position within a file (1-based)."""
118 """Represents a region within a file (1-based)."""
|
| /arkcompiler/ets_runtime/docs/ |
| D | overview.md | 10 The source code compiler of ArkCompiler JS Runtime receives JS source code, based on which ts2abc g…
30 …JS Compiler Subsystem consists of the Stub compiler, optimized compilation framework based on the …
47 …compiler directly converts the source code into high-quality machine code based on the TS type inf…
49 …ilt-in code blocks and constant strings in the future) in Actor instances based on the Actor memor…
51 …cription and the C/C++ implementation library for operating the TS object based on the class decla…
|
| /arkcompiler/runtime_core/static_core/cmake/ |
| D | Testing.cmake | 26 # Target for building all Googletest-based tests:
30 # Googletest-based tests depends on building them:
39 # Add Googletest-based tests to the source tree.
|
| /arkcompiler/runtime_core/cmake/ |
| D | Testing.cmake | 26 # Target for building all Googletest-based tests:
30 # Googletest-based tests depends on building them:
39 # Add Googletest-based tests to the source tree.
|
| /arkcompiler/runtime_core/static_core/compiler/docs/ |
| D | check_elimination_doc.md | 27 2. If based on bounds analysis input of NullCheck is more then 0, check is deleted.
32 If based on bounds analysis input of ZeroCheck isn't equal than 0, check is deleted.
34 If based on bounds analysis input of NegativeCheck is more then 0, check is deleted.
36 If based on bounds analysis input of BoundsCheck is more or equal than 0 and less than length of ar…
|
| /arkcompiler/ets_frontend/arkguard/tools/ |
| D | timesum.py | 33 based on the conditions that the parent event must fully contain the current event
66 Regenerate timestamps (ts) and durations (dur) for events based on their parent relationships.
118 # Flatten the grouped data and adjust timestamps based on parent relationships
126 # Adjust timestamps based on the parent's start time
171 # Regenerate timestamps and durations based on parent relationships
|
| /arkcompiler/runtime_core/static_core/plugins/ets/stdlib/std/containers/ |
| D | README.md | 3 Here are files implementing AVL-tree and TreeMap data structure, based on AVL-tree.
|
| /arkcompiler/runtime_core/static_core/plugins/ets/playground/frontend/src/pages/codeEditor/ |
| D | ArkTSEditor.test.tsx | 65 it('applies correct theme based on context', () => {
70 it('applies correct theme based on context light', () => {
|
12345678910>>...14