rust/compiler/rustc_const_eval/src/interpret/projection.rs, branch 1.66.1https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.66.12022-09-16T11:36:39+00:00Revert "Revert "Rollup merge of #98582 - oli-obk:unconstrained_opaque_type, r=estebank""2022-09-16T11:36:39+00:00Oli Scherergit-spam-no-reply9815368754983@oli-obk.de2022-07-27T11:58:34+00:00urn:sha1:40e2de8c41b17b4813142b669ec083b5ef530dd6
This reverts commit 4a742a691e7dd2522bad68b86fe2fd5a199d5561.
Fix a bunch of typo2022-08-31T10:24:55+00:00Dezhi Wuwu543065657@163.com2022-08-18T02:13:37+00:00urn:sha1:b1430fb7ca499d517d9f4b3b6c5a81442129c88b
This PR will fix some typos detected by [typos].
I only picked the ones I was sure were spelling errors to fix, mostly in
the comments.
[typos]: https://github.com/crate-ci/typos
Rollup merge of #101101 - RalfJung:read-pointer-as-bytes, r=oli-obk2022-08-30T05:56:51+00:00Dylan DPC99973273+Dylan-DPC@users.noreply.github.com2022-08-30T05:56:51+00:00urn:sha1:81f3841cfb5eae52d7914dfebb6a55b5951c5c3c
interpret: make read-pointer-as-bytes a CTFE-only error with extra information
Next step in the reaction to https://github.com/rust-lang/rust/issues/99923. Also teaches Miri to implicitly strip provenance in more situations when transmuting pointers to integers, which fixes https://github.com/rust-lang/miri/issues/2456.
Pointer-to-int transmutation during CTFE now produces a message like this:
```
= help: this code performed an operation that depends on the underlying bytes representing a pointer
= help: the absolute address of a pointer is not known at compile-time, so such operations are not supported
```
r? ``@oli-obk``
interpret: make read-pointer-as-bytes *always* work in Miri2022-08-27T22:37:44+00:00Ralf Jungpost@ralfj.de2022-08-27T18:54:02+00:00urn:sha1:2e172473daefd24631faf3906bd411798d7d8a17
and show some extra information when it happens in CTFE
remove an ineffective check in const_prop2022-08-27T12:53:04+00:00Ralf Jungpost@ralfj.de2022-08-07T14:36:42+00:00urn:sha1:4173e971b8c06d00b5bf9fb0133220cb37cf99daAuto merge of #99472 - RalfJung:provenance, r=oli-obk2022-07-20T16:56:31+00:00borsbors@rust-lang.org2022-07-20T16:56:31+00:00urn:sha1:a7468c60f8dbf5feb23ad840b174d7e57113a846
interpret: rename Tag/PointerTag to Prov/Provenance
We were pretty inconsistent with calling this the "tag" vs the "provenance" of the pointer; I think we should consistently call it "provenance".
r? `@oli-obk`
Revert "Rollup merge of #98582 - oli-obk:unconstrained_opaque_type, r=estebank"2022-07-20T07:55:58+00:00Oli Scherergit-spam-no-reply9815368754983@oli-obk.de2022-07-20T07:55:58+00:00urn:sha1:4a742a691e7dd2522bad68b86fe2fd5a199d5561
This reverts commit 6f8fb911ad504b77549cf3256a09465621beab9d, reversing
changes made to 7210e46dc69a4b197a313d093fe145722c248b7d.
interpret: rename Tag/PointerTag to Prov/Provenance2022-07-19T19:38:32+00:00Ralf Jungpost@ralfj.de2022-07-18T22:47:31+00:00urn:sha1:0ec3269db85938224bdde4834b3a80c0d85b770d
Let's avoid using two different terms for the same thing -- let's just call it "provenance" everywhere.
In Miri, provenance consists of an AllocId and an SbTag (Stacked Borrows tag), which made this even more confusing.
interpret: make some large types not Copy2022-07-18T17:57:35+00:00Ralf Jungpost@ralfj.de2022-07-16T02:58:20+00:00urn:sha1:213a25d975e06fcba28c2e6aab829ef9f16617cfRollup merge of #99259 - RalfJung:visit-a-place, r=oli-obk2022-07-16T20:30:51+00:00Matthias Krügermatthias.krueger@famsik.de2022-07-16T20:30:51+00:00urn:sha1:fa298beb7941eaab01960630bfad13e40317ad00
interpret/visitor: support visiting with a PlaceTy
Finally we can visit a `PlaceTy` in a way that will only do `force_allocation` when needed ti visit a field. :)
r? `@oli-obk`