| /arkcompiler/ets_runtime/ecmascript/ |
| D | js_async_function.cpp | 37 // 1.Let asyncContext be the running execution context. in AsyncFunctionAwait()
84 … // 11.Remove asyncContext from the execution context stack and restore the execution context that in AsyncFunctionAwait()
85 // is at the top of the execution context stack as the running execution context. in AsyncFunctionAwait()
95 // 1.Let asyncContext be the running execution context. in AsyncFunctionAwait()
141 … // 11.Remove asyncContext from the execution context stack and restore the execution context that in AsyncFunctionAwait()
142 // is at the top of the execution context stack as the running execution context. in AsyncFunctionAwait()
160 // 2.Let prevContext be the running execution context. in AsyncFunctionAwaitFulfilled()
162 …// 4.Push asyncContext onto the execution context stack; asyncContext is now the running execution… in AsyncFunctionAwaitFulfilled()
166 …rt: When we reach this step, asyncContext has already been removed from the execution context stack in AsyncFunctionAwaitFulfilled()
167 // and prevContext is the currently running execution context. in AsyncFunctionAwaitFulfilled()
[all …]
|
| D | js_generator_object.cpp | 68 // 5.Let methodContext be the running execution context. in GeneratorResume()
74 …// 8.Push genContext onto the execution context stack; genContext is now the running execution con… in GeneratorResume()
77 …// 10.Assert: When we return here, genContext has already been removed from the execution context … in GeneratorResume()
78 // methodContext is the currently running execution context. in GeneratorResume()
95 …e a generator enters the completed state it never leaves it and its associated execution context is in GeneratorResumeAbrupt()
96 …// never resumed. Any execution state associated with generator can be discarded at this poi… in GeneratorResumeAbrupt()
122 // 6.Let methodContext be the running execution context. in GeneratorResumeAbrupt()
128 …// 9.Push genContext onto the execution context stack; genContext is now the running execution con… in GeneratorResumeAbrupt()
131 …// 11.Assert: When we return here, genContext has already been removed from the execution context … in GeneratorResumeAbrupt()
132 // methodContext is the currently running execution context. in GeneratorResumeAbrupt()
|
| D | js_async_generator_object.cpp | 217 // 14. Let callerContext be the running execution context. in AsyncGeneratorResumeNext()
220 …// 17. Push genContext onto the execution context stack; genContext is now the running execution c… in AsyncGeneratorResumeNext()
224 …// 20. Assert: When we return here, genContext has already been removed from the execution context… in AsyncGeneratorResumeNext()
225 // callerContext is the currently running execution context. in AsyncGeneratorResumeNext()
|
| /arkcompiler/ets_runtime/docs/ |
| D | overview.md | 24 - **JS Execution Subsystem**
26 …JS Execution Subsystem consists of an interpreter that executes bytecodes, inline caching that sto…
43 …ime is designed to provide a JS/TS application execution engine for OpenHarmony rather than a JS e…
45 - To improve the application execution performance and security, ArkCompiler JS Runtime statically …
47 …nformation to statically generate inline caching to accelerate bytecode execution. The TS Ahead of…
|
| /arkcompiler/runtime_core/docs/ |
| D | glossary.md | 13 execution. In case of Panda Runtime, AOT compilation is used to compile Panda Bytecode into
26 execution. In case of Panda Runtime, JIT compilation is used to compile Panda Bytecode into
37 compactness and efficient execution by Panda Runtime. See https://en.wikipedia.org/wiki/Bytecode.
62 * **Safepoint** is a range of execution where the state of the executing thread is well described.
74 GC force to stop execution of code (interpreted,AOTed or JITed) to make exclusively some
|
| D | on-stack-replacement.md | 76 On each OSR entry, we need to restore execution context.
99 …cframe on the stack. When OSR is occurred we call OSR compiled code, and once it finishes execution
100 …the Interpreter. Interpreter, in turn, execute fake `return` instruction to exit from the execution
|
| D | tracing.md | 6 Trace API is described in libpandabase/trace/trace.h file. It supports tracing a scope execution ti…
|
| /arkcompiler/runtime_core/tests/cts-generator/ |
| D | README.md | 10 * `PANDA_CTS_JOBS_NUMBER` - amount of parallel jobs for test execution. Default is 8.
62 -j, --jobs N Amount of concurrent jobs for test execution (default 8)
129 Tests with `release` tag will be included to test execution, with `sanitizer-fail` will be excluded.
165 execution. Update all tests that have `bugid: [number]` and `ignore: true` - remove bugid relation …
|
| /arkcompiler/runtime_core/cmake/ |
| D | README.md | 47 * `compile_commands.json` - json nija-commands file to correct execution clang-tidy.
54 * Script to show diff through clang-format execution - `scripts/run-clang-format.py`
|
| /arkcompiler/runtime_core/tests/cts-generator/cts-template/ |
| D | jnez.obj.yaml | 24 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
389 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
409 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
430 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
495 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
562 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
|
| D | jeqz.obj.yaml | 24 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
389 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
408 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
428 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
495 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
564 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
|
| D | jmp.yaml | 20 …Unconditionally transfer execution to an instruction at offset bytes from the beginning of the cur…
33 … description: Check execution is transferred, jump forward, backward, jump on current instruction.
|
| /arkcompiler/runtime_core/compiler/optimizer/code_generator/ |
| D | encoder.md | 9 There are two major variable-parts - architecture and execution model. Current architecture has aim…
69 ### Execution model (concrete implementation - must be architecture independent)
70 …ust to be able to create default headers for emitted code and implement execution-specific code, e…
148 // 2. Create execution model - must be target independent
|
| /arkcompiler/runtime_core/verification/models/ |
| D | README.md | 24 This file contains two execution modes:
|
| /arkcompiler/runtime_core/compiler/docs/ |
| D | code_sink_doc.md | 8 …optimization allows to avoid execution of statements that are not used on execution path. This sho…
|
| D | aot_cha.md | 68 …, then all other entries of --boot-panda-files that will be used during execution should have been…
86 differ. By this reason, the compiled code has to resolve the method during execution and retrieve i…
|
| /arkcompiler/runtime_core/tests/verifier-tests/ |
| D | cflow_err_beyond_end_of_function.pa | 15 # execution beyond end of function
|
| D | cflow_execution_may_go_beyond_the_end.pa | 16 # execution may go beyond the end
|
| /arkcompiler/runtime_core/compiler/tests/x86/ |
| D | asmjit_test.cpp | 28 // Runtime designed for JIT code execution. in TEST_F()
53 // Runtime designed for JIT code execution. in TEST_F()
|
| /arkcompiler/runtime_core/runtime/arch/x86/ |
| D | interpreter_support.S | 16 // call implemented interpreter execution directly
|
| /arkcompiler/ets_frontend/ts2panda/src/function/ |
| D | asyncGeneratorFunctionBuilder.ts | 113 …/** 27.6.3.8.7 Remove genContext from the execution context stack and restore the execution contex…
114 * is at the top of the execution context stack as the running execution context.
|
| /arkcompiler/runtime_core/tests/cts-generator/runner/ |
| D | single_test_runner.rb | 195 def execution method
345 # 6) Execution
346 execution
|
| /arkcompiler/runtime_core/cross_values/ |
| D | diff_check_values.sh | 15 # At the moment, the script is nothing more than `diff` execution.
|
| /arkcompiler/runtime_core/docs/diagrams/ |
| D | static-analyzer-warnings-generation.puactivity | 25 ->build Exploded Graph(symbolic execution of CFG);
|
| /arkcompiler/ets_frontend/es2panda/compiler/function/ |
| D | functionBuilder.cpp | 77 …/** 27.6.3.8.7 Remove genContext from the execution context stack and restore the execution contex… in AsyncYield()
78 * is at the top of the execution context stack as the running execution context. in AsyncYield()
|