• Kunshan Wang's avatar
    Emphasise what "iref" is and what it can refer to. · 643ac0b3
    Kunshan Wang authored
    IRef refers to any memory location in any parts of the Mu memory,
    including both heap, stack and global. The common part about them is
    that Mu knows the types (at least the location of reference fields) of
    all of them. We use the term "conceptually boxed" and "conceptually
    unboxed" to describe the difference between the destination of "iref"
    and "uptr": irefs always refer into "conceptually boxed" things (boxed
    in the sense that Mu knows their field types (at least reference
    fields)). Heap objects are obviously boxed. We can consider each stack
    as a huge box, and the entire global space as a huge box. "iref" can
    only be obtained from the allocation operations in Mu. But uptrs may
    point outside the Mu memory, which can be literally anywhere. They can
    even be created by C functions, such as "malloc".
    643ac0b3
Name
Last commit
Last update
scripts Loading commit data...
.gitignore Loading commit data...
README.rst Loading commit data...
_Sidebar.md Loading commit data...
api.rst Loading commit data...
bootimage.rst Loading commit data...
common-insts.rst Loading commit data...
faq.rst Loading commit data...
hail.rst Loading commit data...
instruction-set.rst Loading commit data...
ir-binary.rst Loading commit data...
ir.rst Loading commit data...
irbuilder.rst Loading commit data...
memory-model.rst Loading commit data...
memory.rst Loading commit data...
muapi.h Loading commit data...
native-interface-x64-unix.rst Loading commit data...
native-interface.rst Loading commit data...
overview.rst Loading commit data...
portability.rst Loading commit data...
threads-stacks.rst Loading commit data...
type-system.rst Loading commit data...