Home
last modified time | relevance | path

Searched full:managed (Results 1 – 25 of 41) sorted by relevance

12

/arkcompiler/runtime_core/verification/config/
DREADME.md3 ### Debug_breakpoint for managed code
5 Debug_breakpoint for managed code are used to stop GDB just right before processing
6 instruction at specified offset in managed code
/arkcompiler/runtime_core/docs/
Druntime-compiled_code-interaction.md17 Panda runtime as a set of functions aimed to execute managed code. The runtime consists of several …
20 The interpreter is a part of the runtime aimed to execute bytecode of managed functions. The interp…
21 hotness counter (see [Structure of `panda::Method`](#structure-of-pandamethod)) of managed function…
23 The compiler is aimed to translate managed function's bytecode to native code. The compiler has an …
28 Panda runtime and managed code must call functions according to the target calling convention.
29 Compiled code of a managed function must accept one extra argumnent: the pointer to `panda::Method`…
61 `panda::Method` describes a managed function in the runtime.
66 | hotness_counter_ | A hotness counter of the managed function. |
70 The field `hotness_counter_` reflects hotness of a managed function. The interpreter increments it …
78 The managed function could have compiled code or it could be executed by the interpreter.
[all …]
Dpanda-runtime.md30 * [Overview of Managed Assemblers](overview-of-managed-assemblers.md)
Druntime-class.md5 Pointer to the managed class object (instance of `panda.Class` or other in case of plugin-related c…
11 We store common runtime information separately from managed object to give more flexebility for its…
34 | `Managed Object` |---+
Ddesign-of-interpreter.md127 1. Interpreter is stackless (from the host stack perspective): Whenever a call from managed code
128 to managed code is performed, no new host frame is created for the interpreter itself.
190 managed application have to think about this limitation, which contradicts the idea of
191 portability of managed applications. Configurable virtual stack implementation relaxes this
216 A general overview of managed assembly languages can be found [here](overview-of-managed-assemblers…
Dcode_metainfo.md120 | ROOTS_REG_MASK_INDEX | Mask of the CPU registers that hold managed objects |
121 | ROOTS_STACK_MASK_INDEX | Mask of the stack slots that hold managed objects |
156 …itmap table, where column is a bit mask, that determines which CPU register holds a managed object.
160 … Bitmap table, where column is a bit mask, that determines which stack slot holds a managed object.
/arkcompiler/runtime_core/runtime/include/
Dexceptions.h29 // This function could be used in case there are no managed stack frames.
32 // get current executing method from the managed stack.
Dmanaged_thread.h27 * \brief Class represents managed thread
30 * runtime knows about all managed threads at any given time.
33 * is necessary to execute managed code:
146 * @return pointer to ManagedThread or nullptr (if current thread is not a managed thread)
182 …// If a daemon thread with NATIVE status was deregistered, it should not access any managed object, in UpdateStatus()
853 // end of stack for managed thread, throw exception if native stack grow over it
Dmtmanaged_thread.h157 * @return pointer to MTManagedThread or nullptr (if current thread is not a managed thread)
/arkcompiler/runtime_core/runtime/include/coretypes/
Darray-inl.h156 …td::is_arithmetic_v<T> || IS_REF, "T should be arithmetic type or pointer to managed object type"); in Set()
176 …td::is_arithmetic_v<T> || IS_REF, "T should be arithmetic type or pointer to managed object type"); in Get()
194 …td::is_arithmetic_v<T> || IS_REF, "T should be arithmetic type or pointer to managed object type"); in Set()
212 …td::is_arithmetic_v<T> || IS_REF, "T should be arithmetic type or pointer to managed object type"); in Get()
/arkcompiler/runtime_core/compiler/optimizer/code_generator/
Dframe_info.h90 // SetupFrame - setup CFrame (aka. 'managed' frame).
128 // i.e. a prologue for managed code.
/arkcompiler/ets_runtime/ecmascript/taskpool/
Dtask.h28 // Tasks not managed by VM
/arkcompiler/runtime_core/runtime/mem/
Drendezvous.h27 /** Meeting point for all managed threads.
Dobject_helpers-inl.h38 // The offset is relative to the class. Adjust it to make relative to the managed object in TraverseClass()
/arkcompiler/ets_runtime/ecmascript/
Dwaiter_list.h41 // Managed Arraybuffer or SharedArrayBuffer memory data
Decma_handle_scope.h62 // Each Handle must be managed by HandleScope, otherwise it may cause Handle leakage. in NewHandle()
/arkcompiler/runtime_core/runtime/tests/
Dthread_test.cpp78 * managed #1
/arkcompiler/runtime_core/runtime/include/tooling/
Ddebug_interface.h237 * \brief Method is called by the runtime when managed thread is attached to it
243 * \brief Method is called by the runtime when managed thread is detached
472 * \brief Enumerates managed frames in the thread \param threadId
/arkcompiler/runtime_core/compiler/optimizer/ir/
Druntime_interface.h539 * managed Thread object information
643 // Offset of the managed object in the BaseClass
798 // Return offset of the managed object in the class
804 // Return offset of the managed object in the class
/arkcompiler/runtime_core/runtime/mem/gc/
Dcard_table-inl.h71 …// global Mutator lock held, so all previous managed thread's writes should be visible by GC thread in VisitMarked()
/arkcompiler/runtime_core/runtime/mem/refstorage/
Dreference_storage.h161 * it should be only used in Managed code(with ScopedObjectFix).
/arkcompiler/ets_runtime/
DLICENSE58 and issue tracking systems that are managed by, or on behalf of, the
/arkcompiler/toolchain/
DLICENSE58 and issue tracking systems that are managed by, or on behalf of, the
/arkcompiler/runtime_core/
DLICENSE58 and issue tracking systems that are managed by, or on behalf of, the
/arkcompiler/runtime_core/runtime/
Dthread_manager.h40 MANAGED_CODE_THREAD = 2, // Thread which can execute managed code

12