Documentation

Miri.Input.CompilerVTableMachine

Imported/dynamic symbolic vtables share canonical type/predicate identities and the same actual allocation/address engine. Compiler query leaves stay typed.

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
      Equations
      • One or more equations did not get rendered due to their size.
      Instances For

        Runtime symbolic maps must wrap the imported queries: reversing this order would lose freshly reserved function/vtable identities after successful casts.

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

          Production compiler/vtable leaves require no runtime-operation scaffold.

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

            Close virtual receiver/type selection, dynamic drop, caller location and actual function-pointer resolution on the canonical call state.

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

              Unsize/upcast casts create and inspect actual symbolic vtables and actual function pointers; compiler layout/type queries remain the source provider.

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

                Validity preserves FnVal.Other for source get_ptr_fn checks while compiler virtual method entries retain full Instance identities.

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