Documentation

Miri.Input.EvalDynamicMemory

Dynamic memory layout on the actual machine state. Canonical type identity survives the memory view; symbolic vtable reads need no invented stack or placeholder full vtable dictionary. Every failing dynamic query retains its StepError through AccessState.pendingError, including UB classifications.

@[reducible, inline]
abbrev Miri.Input.EvalDynamicMemory.User (Os R P H D O Aff B Host : Type) :
Equations
Instances For
    @[reducible, inline]
    abbrev Miri.Input.EvalDynamicMemory.Machine (Os R P H D O Aff B Host : Type) :
    Equations
    Instances For
      def Miri.Input.EvalDynamicMemory.arrays {Os R P H D O Aff B Host : Type} :
      RuntimeArrayQueries.Access (Machine Os R P H D O Aff B Host)
      Equations
      • One or more equations did not get rendered due to their size.
      Instances For

        Only source symbolic read operations: resolve identity, look up the actual registry/imported vtable, compare normalized predicates and query its layout.

        Equations
        • One or more equations did not get rendered due to their size.
        Instances For
          Equations
          • One or more equations did not get rendered due to their size.
          Instances For

            The source operation runs on the real machine carried by the memory context. No layout-equality search or synthetic interpreter frame is used.

            Equations
            • One or more equations did not get rendered due to their size.
            Instances For