diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-12-02 04:09:00 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-12-02 04:09:00 +0100 |
| commit | fd09fad064504e18cd7fd15ccd7c957787482b81 (patch) | |
| tree | 8c4114ca2afdc2149bffbdb2b8e4c7474afbfa38 /src/test/debuginfo/enum-thinlto.rs | |
| parent | a279ebbc9199d81d1c4ffc87c41c9544ea905115 (diff) | |
| parent | a9976d89ed721184a95a24f109a65916f2905793 (diff) | |
| download | rust-fd09fad064504e18cd7fd15ccd7c957787482b81.tar.gz rust-fd09fad064504e18cd7fd15ccd7c957787482b81.zip | |
Rollup merge of #66789 - eddyb:mir-source-scope-local-data, r=oli-obk
rustc: move mir::SourceScopeLocalData to a field of SourceScopeData. By having one `ClearCrossCrate<SourceScopeLocalData>` for each scope, as opposed to a single `ClearCrossCrate` for all the `SourceScopeLocalData`s, we can represent the fact that some scopes have `SourceScopeLocalData` associated with them, and some don't. This is useful when doing MIR inlining across crates, because the `ClearCrossCrate` will be `Clear` for the cross-crate MIR scopes and `Set` for the local ones. Also see https://github.com/rust-lang/rust/pull/66203#issuecomment-555589574 for some context around this approach. Fixes #51314.
Diffstat (limited to 'src/test/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions