Searched full:managed (Results 1 – 25 of 30) sorted by relevance
12
| /ark/runtime_core/verification/debug/ |
| D | README.md | 3 ### Breakpoints for managed code
5 Breakpoints for managed code are used to stop GDB just right before processing
6 instruction at specified offset in managed code.
|
| /ark/runtime_core/docs/ |
| D | runtime-compiled_code-interaction.md | 15 Panda runtime is a set of functions used to execute managed code. The runtime consists of several m…
18 The interpreter, as a part of runtime, executes bytecodes of managed functions and manages hotness
19 counter (see [Structure of `panda::Method`](#structure-of-pandamethod)) of managed functions.
21 The compiler translates bytecodes of managed functions to native code. The compiler provides
26 Panda runtime and managed code must call functions according to the target calling convention.
27 Compiled code of a managed function must accept one extra argument: the pointer to `panda::Method` …
59 `panda::Method` describes a managed function in the runtime.
64 | hotness_counter_ | A hotness counter of the managed function. |
68 The field `hotness_counter_` reflects hotness of a managed function. The interpreter increments it …
76 The managed function may have compiled code or be executed by the interpreter.
[all …]
|
| D | runtime-class.md | 5 Pointer to the managed class object (instance of `panda.Class` or `java.lang.Class` in case of Java…
11 Storing common runtime information separately from managed objects allows more flexibility for the …
34 | `Managed Object` |---+
|
| D | design-of-interpreter.md | 114 1. Interpreter is stackless (from the host stack perspective): Whenever a call from managed code
115 to managed code is performed, no new host frame is created for the interpreter itself.
177 managed applications have to think about this limitation, which contradicts the idea of
178 … portability of managed applications. We can relax this constraint to some extent with configurable
|
| D | runtime-debug-api.md | 26 * `StartProcess` - occurs when the managed process is started or failed to start
|
| /ark/runtime_core/runtime/include/ |
| D | exceptions.h | 29 // This function could be used in case there are no managed stack frames.
32 // get current executing method from the managed stack.
|
| D | managed_thread.h | 30 * \brief Class represents managed thread
33 * runtime knows about all managed threads at any given time.
36 * is necessary to execute managed code:
145 * @return pointer to ManagedThread or nullptr (if current thread is not a managed thread)
|
| D | thread.h | 137 * ManagedThread - stores runtime context to run managed code in single-threaded environment
|
| D | mtmanaged_thread.h | 195 * @return pointer to MTManagedThread or nullptr (if current thread is not a managed thread)
|
| /ark/runtime_core/runtime/include/coretypes/ |
| D | array-inl.h | 166 …td::is_arithmetic_v<T> || IS_REF, "T should be arithmetic type or pointer to managed object type"); in Set()
187 …td::is_arithmetic_v<T> || IS_REF, "T should be arithmetic type or pointer to managed object type"); in Get()
206 …td::is_arithmetic_v<T> || IS_REF, "T should be arithmetic type or pointer to managed object type"); in Set()
225 …td::is_arithmetic_v<T> || IS_REF, "T should be arithmetic type or pointer to managed object type"); in Get()
|
| /ark/js_runtime/ecmascript/trampoline/ |
| D | call_trampoline_amd64.S | 52 pushq %rsi // prev managed fp
86 popq %rsi // pop prev-managed frame
|
| /ark/js_runtime/ecmascript/ |
| D | ecma_handle_scope-inl.h | 42 // Each Handle must be managed by HandleScope, otherwise it may cause Handle leakage. in NewHandle()
|
| /ark/runtime_core/runtime/include/tooling/ |
| D | debug_interface.h | 235 * \brief Method is called by the runtime when managed thread is attached to it
241 * \brief Method is called by the runtime when managed thread is detached
418 * \brief Enumerates managed frames in the thread \param threadId
|
| /ark/runtime_core/runtime/tests/ |
| D | thread_test.cpp | 78 * managed #1
|
| /ark/runtime_core/runtime/ |
| D | thread.cpp | 95 /* static - creation of the initial Managed thread */
106 /* static - creation of the initial MT Managed thread */
275 // Since we don't allow two consecutive NativeCode frames, there is no managed code on stack if
|
| D | runtime.yaml | 14 # Mapping beetween managed core types and C++ mirror classes
|
| D | signal_handler.cpp | 87 LOG(ERROR, RUNTIME) << "Managed thread segmentation fault"; in DumpStackTrace()
|
| D | thread_manager.h | 47 …4, // Thread which can execute managed code - should be used with JAVA_THREAD and/or JS_T…
|
| /ark/runtime_core/runtime/mem/refstorage/ |
| D | reference_storage.h | 159 * it should be only used in Managed code(with ScopedObjectFix).
|
| /ark/js_runtime/ |
| D | LICENSE | 58 and issue tracking systems that are managed by, or on behalf of, the
|
| /ark/runtime_core/ |
| D | LICENSE | 58 and issue tracking systems that are managed by, or on behalf of, the
|
| D | CMakeLists.txt | 124 # ----- Bootstrapping (for parts of platform written in managed code ) ---------
|
| /ark/ts2abc/ |
| D | LICENSE | 58 and issue tracking systems that are managed by, or on behalf of, the
|
| /ark/runtime_core/runtime/mem/ |
| D | runslots_allocator.h | 229 * Current implementation limits the amount of memory pools which can be managed by this class.
|
| /ark/runtime_core/verification/ |
| D | messages.yaml | 653 …Added config for managed breakpoint for '${method_name}' (hash 0x${std::hex << hash}), offset 0x${…
|
12