pub enum MirPhase {
    Built,
    Analysis(AnalysisPhase),
    Runtime(RuntimePhase),
}
Expand description

Represents the “flavors” of MIR.

All flavors of MIR use the same data structure, but there are some important differences. These differences come in two forms: Dialects and phases.

Dialects represent a stronger distinction than phases. This is because the transitions between dialects are semantic changes, and therefore technically lowerings between distinct IRs. In other words, the same Body might be well-formed for multiple dialects, but have different semantic meaning and different behavior at runtime.

Each dialect additionally has a number of phases. However, phase changes never involve semantic changes. If some MIR is well-formed both before and after a phase change, it is also guaranteed that it has the same semantic meaning. In this sense, phase changes can only add additional restrictions on what MIR is well-formed.

When adding phases, remember to update MirPhase::phase_index.

Variants

Built

The MIR that is generated by MIR building.

The only things that operate on this dialect are unsafeck, the various MIR lints, and const qualifs.

This has no distinct phases.

Analysis(AnalysisPhase)

The MIR used for most analysis.

The only semantic change between analysis and built MIR is constant promotion. In built MIR, sequences of statements that would generally be subject to constant promotion are semantically constants, while in analysis MIR all constants are explicit.

The result of const promotion is available from the mir_promoted and promoted_mir queries.

This is the version of MIR used by borrowck and friends.

Runtime(RuntimePhase)

The MIR used for CTFE, optimizations, and codegen.

The semantic changes that occur in the lowering from analysis to runtime MIR are as follows:

  • Drops: In analysis MIR, Drop terminators represent conditional drops; roughly speaking, if dataflow analysis determines that the place being dropped is uninitialized, the drop will not be executed. The exact semantics of this aren’t written down anywhere, which means they are essentially “what drop elaboration does.” In runtime MIR, the drops are unconditional; when a Drop terminator is reached, if the type has drop glue that drop glue is always executed. This may be UB if the underlying place is not initialized.
  • Packed drops: Places might in general be misaligned - in most cases this is UB, the exception is fields of packed structs. In analysis MIR, Drop(P) for a P that might be misaligned for this reason implicitly moves P to a temporary before dropping. Runtime MIR has no such rules, and dropping a misaligned place is simply UB.
  • Unwinding: in analysis MIR, unwinding from a function which may not unwind aborts. In runtime MIR, this is UB.
  • Retags: If -Zmir-emit-retag is enabled, analysis MIR has “implicit” retags in the same way that Rust itself has them. Where exactly these are is generally subject to change, and so we don’t document this here. Runtime MIR has all retags explicit.
  • Generator bodies: In analysis MIR, locals may actually be behind a pointer that user code has access to. This occurs in generator bodies. Such locals do not behave like other locals, because they eg may be aliased in surprising ways. Runtime MIR has no such special locals - all generator bodies are lowered and so all places that look like locals really are locals.
  • Const prop lints: The lint pass which reports eg 200_u8 + 200_u8 as an error is run as a part of analysis to runtime MIR lowering. This means that transformations which may supress such errors may not run on analysis MIR.

Implementations

Gets the index of the current MirPhase within the set of all MirPhases.

FIXME(JakobDegen): Return a (usize, usize) instead.

Trait Implementations

Returns a copy of the value. Read more
Performs copy-assignment from source. Read more
Formats the value using the given formatter. Read more
This method returns an Ordering between self and other. Read more
Compares and returns the maximum of two values. Read more
Compares and returns the minimum of two values. Read more
Restrict a value to a certain interval. Read more
This method tests for self and other values to be equal, and is used by ==. Read more
This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason. Read more
This method returns an ordering between self and other values if one exists. Read more
This method tests less than (for self and other) and is used by the < operator. Read more
This method tests less than or equal to (for self and other) and is used by the <= operator. Read more
This method tests greater than (for self and other) and is used by the > operator. Read more
This method tests greater than or equal to (for self and other) and is used by the >= operator. Read more
The entry point for folding. To fold a value t with a folder f call: t.try_fold_with(f). Read more
A convenient alternative to try_fold_with for use with infallible folders. Do not override this method, to ensure coherence with try_fold_with. Read more
The entry point for visiting. To visit a value t with a visitor v call: t.visit_with(v). Read more
Returns true if self has any late-bound regions that are either bound by binder or bound by some binder outside of binder. If binder is ty::INNERMOST, this indicates whether there are any late-bound regions that appear free. Read more
Returns true if this self has any regions that escape binder (and hence are not bound by it). Read more
“Free” regions in this context means that it has any region that is not (a) erased or (b) late-bound. Read more
True if there are any un-erased free regions.
Indicates whether this value references only ‘global’ generic parameters that are the same regardless of what fn we are in. This is used for caching. Read more
True if there are any late-bound regions
Indicates whether this value still has parameters/placeholders/inference variables which could be replaced later, in a way that would change the results of impl specialization. Read more

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more
Immutably borrows from an owned value. Read more
Mutably borrows from an owned value. Read more
This method turns the parameters of a DepNodeConstructor into an opaque Fingerprint to be used in DepNode. Not all DepNodeParams support being turned into a Fingerprint (they don’t need to if the corresponding DepNode is anonymous). Read more
This method tries to recover the query key from the given DepNode, something which is needed when forcing DepNodes during red-green evaluation. The query system will only call this method if fingerprint_style() is not FingerprintStyle::Opaque. It is always valid to return None here, in which case incremental compilation will treat the query as having changed instead of forcing it. Read more

Returns the argument unchanged.

Calls U::from(self).

That is, this conversion is whatever the implementation of From<T> for U chooses to do.

The resulting type after obtaining ownership.
Creates owned data from borrowed data, usually by cloning. Read more
Uses borrowed data to replace owned data, usually by cloning. Read more
The type returned in the event of a conversion error.
Performs the conversion.
The type returned in the event of a conversion error.
Performs the conversion.

Layout

Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference’s “Type Layout” chapter for details on type layout guarantees.

Size: 2 bytes

Size for each variant:

  • Built: 0 bytes
  • Analysis: 1 byte
  • Runtime: 1 byte