rustc_middle::mir::interpret

Module error

source

Macros§

Structs§

Enums§

  • Details of which pointer is not aligned.
  • Details of why a pointer had to be in-bounds.
  • Error information for when the program we executed turned out not to actually be a valid program. This cannot happen in stand-alone Miri (except for layout errors that are only detect during monomorphization), but it can happen during CTFE/ConstProp where we work on generic code or execution does not have all information available.
  • Error information for when the program exhausted the resources granted to it by the interpreter.
  • Error information for when the program caused Undefined Behavior.
  • Error information for when the program did something that might (or might not) be correct to do according to the Rust spec, but due to limitations in the interpreter, the operation could not be carried out. These limitations can differ between CTFE and the Miri engine, e.g., CTFE does not support dereferencing pointers at integral addresses.

Traits§

  • A trait for machine-specific errors (or other “machine stop” conditions).

Functions§

Type Aliases§