about summary refs log tree commit diff
path: root/tests/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs
diff options
context:
space:
mode:
authorDylan DPC <99973273+Dylan-DPC@users.noreply.github.com>2022-03-25 01:34:29 +0100
committerGitHub <noreply@github.com>2022-03-25 01:34:29 +0100
commitc66e0c87267859a46f1a8851f30892985760cfd6 (patch)
tree6f4ad2c8f2abd0ad0819e5d9878f3725451815af /tests/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs
parentd1d4613ead1896eff612903edb5da42630821b29 (diff)
parent26d7b8ddb2d323e2d6cb77c04caf7c58ce5af267 (diff)
downloadrust-c66e0c87267859a46f1a8851f30892985760cfd6.tar.gz
rust-c66e0c87267859a46f1a8851f30892985760cfd6.zip
Rollup merge of #94655 - JakobDegen:mir-phase-docs, r=oli-obk
Clarify which kinds of MIR are allowed during which phases.

This enhances documentation with these details and extends the validator to check these requirements more thoroughly. Most of these conditions were already being checked.

There was also some disagreement between the `MirPhase` docs and validator as to what it meant for the `body.phase` field to have a certain value. This PR resolves those disagreements in favor of the `MirPhase` docs (which is what the pass manager implemented), adjusting the validator accordingly. The result is now that the `DropLowering` phase begins with the end of the elaborate drops pass, and lasts until the beginning of the generator lowring pass. This doesn't feel entirely natural to me, but as long as it's documented accurately it should be ok.

r? rust-lang/mir-opt
Diffstat (limited to 'tests/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs')
0 files changed, 0 insertions, 0 deletions