Searched full:execution (Results 1 – 25 of 73) sorted by relevance
123
| /ark/js_runtime/ecmascript/ |
| D | js_async_function.cpp | 35 // 1.Let asyncContext be the running execution context. in AsyncFunctionAwait()
77 … // 11.Remove asyncContext from the execution context stack and restore the execution context that in AsyncFunctionAwait()
78 // is at the top of the execution context stack as the running execution context. in AsyncFunctionAwait()
91 // 2.Let prevContext be the running execution context. in AsyncFunctionAwaitFulfilled()
94 …// 4.Push asyncContext onto the execution context stack; asyncContext is now the running execution… in AsyncFunctionAwaitFulfilled()
99 …// 6.Assert: When we reach this step, asyncContext has already been removed from the execution con… in AsyncFunctionAwaitFulfilled()
100 // and prevContext is the currently running execution context. in AsyncFunctionAwaitFulfilled()
112 // 2.Let prevContext be the running execution context. in AsyncFunctionAwaitRejected()
115 …// 4.Push asyncContext onto the execution context stack; asyncContext is now the running execution… in AsyncFunctionAwaitRejected()
121 …// 6.Assert: When we reach this step, asyncContext has already been removed from the execution con… in AsyncFunctionAwaitRejected()
[all …]
|
| D | js_generator_object.cpp | 67 // 5.Let methodContext be the running execution context. in GeneratorResume()
73 …// 8.Push genContext onto the execution context stack; genContext is now the running execution con… in GeneratorResume()
78 …// 10.Assert: When we return here, genContext has already been removed from the execution context … in GeneratorResume()
79 // methodContext is the currently running execution context. in GeneratorResume()
97 …e a generator enters the completed state it never leaves it and its associated execution context is in GeneratorResumeAbrupt()
98 …// never resumed. Any execution state associated with generator can be discarded at this poi… in GeneratorResumeAbrupt()
124 // 6.Let methodContext be the running execution context. in GeneratorResumeAbrupt()
130 …// 9.Push genContext onto the execution context stack; genContext is now the running execution con… in GeneratorResumeAbrupt()
135 …// 11.Assert: When we return here, genContext has already been removed from the execution context … in GeneratorResumeAbrupt()
136 // methodContext is the currently running execution context. in GeneratorResumeAbrupt()
|
| D | js_array.cpp | 121 // Let thisRealm be the running execution context’s Realm. in ArraySpeciesCreate()
165 // a Realm that is not the Realm of the running execution context, then a new Array is in ArraySpeciesCreate()
166 // created using the Realm of the running execution context. This maintains compatibility in ArraySpeciesCreate()
|
| /ark/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 | design-of-interpreter.md | 25 1. Program execution via bytecode interpretation should be enabled on all targets.
119 1. Interpreters are by nature slower than native code execution. Slowdown can be explained by:
126 1. An ideal target would be 5x-10x slowdown factor (compared to native execution)
|
| D | tracing.md | 6 …bed in the libpandabase/trace/trace.h file. It supports tracing a scope execution time and trackin…
|
| D | runtime-compiled_code-interaction.md | 5 Compiled code and Panda runtime interact with each other during execution. This document describes …
131 - data - arbitrary data necessary for function execution. It is optional.
184 * Adjusts the Stack Pointer, and pass execution to the runtime function.
383 There may be a situation when compiled code cannot continue execution for some reason.
384 For such cases compiled code must call `void Deoptimize()` runtime entrypoint to continue execution…
|
| /ark/runtime_core/tests/cts-generator/ |
| D | README.md | 10 * `PANDA_CTS_JOBS_NUMBER` - amount of parallel jobs for test execution. Default is 8.
53 -j, --jobs N Amount of concurrent jobs for test execution (default 8)
123 Tests with `release` tag will be included to test execution, with `clang_release_sanitizer` will be…
159 execution. Update all tests that have `bugid: [number]` and `ignore: true` - remove bugid relation …
|
| D | test-runner.rb | 93 opts.on('-j', '--jobs N', 'Amount of concurrent jobs for test execution (default 8)', Integer)
209 # TestRunner::Result holds execution statistic
279 puts "Global timeout reached, finish test execution"
|
| /ark/js_runtime/docs/ |
| D | overview.md | 25 - Execution Engine
27 …The Execution Engine consists of an interpreter that executes bytecodes, Inline Caches that store …
44 … uses the type information to statically generate an inline cache to accelerate bytecode execution.
|
| D | overview-zh.md | 25 - Execution Engine
|
| /ark/runtime_core/cmake/ |
| D | README.md | 66 * `compile_commands.json` - json nija-commands file to correct execution clang-tidy.
73 * Script to show diff through clang-format execution - `build/run-clang-format.py`
|
| /ark/runtime_core/tests/cts-generator/cts-template/ |
| 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.
|
| D | jeqz.obj.yaml | 24 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
281 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
300 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
367 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
|
| D | jnez.obj.yaml | 24 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
281 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
301 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
366 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
|
| D | jeq.obj.yaml | 24 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
658 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
732 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
846 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
|
| D | jne.obj.yaml | 24 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
660 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
735 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
850 …Transfer execution to an instruction at offset bytes from the beginning of the current instruction…
|
| /ark/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
|
| /ark/runtime_core/verification/models/ |
| D | README.md | 24 This file contains two execution modes:
|
| /ark/runtime_core/runtime/arch/x86/ |
| D | interpreter_support.S | 16 // call implemented interpreter execution directly
|
| /ark/runtime_core/docs/diagrams/ |
| D | static-analyzer-warnings-generation.puactivity | 25 ->build Exploded Graph(symbolic execution of CFG);
|
| /ark/ts2abc/test262/ |
| D | README.md | 65 After the execution finished, a directory named `test_es51` is created under directory `test262/dat…
159 * After the execution finished, the following files are generated under directory `out/test262/` (y…
|
| /ark/runtime_core/tests/cts-coverage-tool/ |
| D | non_testable.yaml | 112 pass values of arguments and continue execution from the first instruction of
|
| /ark/runtime_core/runtime/ |
| D | options.yaml | 400 description: Print the start time of command execution
484 description: if enabled then fail execution if heap verifier found heap corruption
|
123