- 12 9月, 2019 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 10 9月, 2019 2 次提交
-
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
- 04 9月, 2019 1 次提交
-
-
由 Albin Stjerna 提交于
-
- 22 7月, 2019 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 20 7月, 2019 4 次提交
-
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
- 25 6月, 2019 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 18 6月, 2019 1 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
- 14 6月, 2019 1 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
- 12 6月, 2019 4 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
- 10 6月, 2019 1 次提交
-
-
由 Jad Ghalayini 提交于
-
- 29 5月, 2019 1 次提交
-
-
The commit should have changed comments as well. At the time of writting, it passes the tidy and check tool. Revisions asked by eddyb : - Renamed of all the occurences of {visit/super}_mir - Renamed test structures `CachedMir` to `Cached` Fixing the missing import on `AggregateKind`
-
- 26 5月, 2019 2 次提交
-
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
- 24 5月, 2019 1 次提交
-
-
由 Edd Barrett 提交于
Once upon a time (commit 9bd35c07) there were two kinds of projection: one for places, and one for constants. It therefore made sense to share the `Projection` struct for both. Although the different use-cases used different concrete types, sharing was made possible by type-parameterisation of `Projection`. Since then, however, the usage of projections in constants has disappeared, meaning that (forgetting lifetimes for a moment) the parameterised type is only every instantiated under one guise. So it may as well be a concrete type.
-
- 04 4月, 2019 1 次提交
-
-
由 flip1995 提交于
-
- 03 4月, 2019 2 次提交
-
-
由 Nicholas Nethercote 提交于
The `InlineAsm` variant is extremely rare, and `mir::Statement` often contributes significantly to peak memory usage.
-
由 Tyler Mandry 提交于
-
- 18 3月, 2019 1 次提交
-
-
由 Saleem Jaffer 提交于
-
- 01 3月, 2019 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 26 12月, 2018 1 次提交
-
-
由 Mark Rousskov 提交于
-
- 18 12月, 2018 1 次提交
-
-
由 Ralf Jung 提交于
-
- 02 12月, 2018 1 次提交
-
-
由 Mark Mansi 提交于
-
- 18 11月, 2018 1 次提交
-
-
由 Matthew Jasper 提交于
Since lexical MIR borrow check is gone, and validation no longer uses these, they can be removed.
-
- 07 11月, 2018 1 次提交
-
-
由 Ralf Jung 提交于
-
- 04 11月, 2018 1 次提交
-
-
由 David Wood 提交于
This commit makes two changes: First, it updates the dataflow builder to add an init for the place containing a union if there is an assignment into the field of that union. Second, it stops a "use of uninitialized" error occuring when there is an assignment into the field of an uninitialized union that was previously initialized. Making this assignment would re-initialize the union, as tested in `src/test/ui/borrowck/borrowck-union-move-assign.nll.stderr`. The check for previous initialization ensures that we do not start supporting partial initialization yet (cc #21232, #54499, #54986).
-
- 01 11月, 2018 1 次提交
-
-
由 Nicholas Nethercote 提交于
This reduces allocation counts significantly in a few benchmarks, reducing instruction counts by up to 2%.
-
- 29 10月, 2018 1 次提交
-
-
由 Ralf Jung 提交于
Also "rename" -Zmir-emit-validate to -Zmir-emit-retag, which is just a boolean (yes or no).
-
- 19 10月, 2018 2 次提交
-
-
由 Oliver Scherer 提交于
-
由 Oliver Scherer 提交于
-
- 17 10月, 2018 1 次提交
-
-
由 Levente Kurusa 提交于
E0669 refers to a constraint that cannot be coerced into a single LLVM value, unfortunately right now this uses the Span for the entire inline assembly statement, which is less than ideal. This commit preserves the Span from HIR, which lets us emit the error using the Span for the operand itself in MIR. Signed-off-by: NLevente Kurusa <lkurusa@acm.org>
-
- 04 10月, 2018 1 次提交
-
-
由 Matthew Jasper 提交于
-
- 24 9月, 2018 1 次提交
-
-
由 Nicholas Nethercote 提交于
This shrinks StatementKind from 64 bytes to 48 bytes on 64-bit.
-
- 18 9月, 2018 1 次提交
-
-
由 Remy Rakic 提交于
-