rust/compiler/rustc_mir/src/interpret/validity.rs, branch 1.56.0 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.56.0 2021-08-25T02:17:41+00:00 Auto merge of #88242 - bonega:allocation_range, r=oli-obk 2021-08-25T02:17:41+00:00 bors bors@rust-lang.org 2021-08-25T02:17:41+00:00 urn:sha1:e5484cec0e3f60b2a0010505cd355639f75a2973 Use custom wrap-around type instead of RangeInclusive Two reasons: 1. More memory is allocated than necessary for `valid_range` in `Scalar`. The range is not used as an iterator and `exhausted` is never used. 2. `contains`, `count` etc. methods in `RangeInclusive` are doing very unhelpful(and dangerous!) things when used as a wrap-around range. - In general this PR wants to limit potentially confusing methods, that have a low probability of working. Doing a local perf run, every metric shows improvement except for instructions. Max-rss seem to have a very consistent improvement. Sorry - newbie here, probably doing something wrong. Rename to WrappingRange 2021-08-23T12:24:34+00:00 Andreas Liljeqvist bonega@gmail.com 2021-08-23T12:24:34+00:00 urn:sha1:e8e6d9bd86c9cf685666718ca99e016275e1751b Use ref 2021-08-23T12:18:48+00:00 Andreas Liljeqvist bonega@gmail.com 2021-08-23T12:18:48+00:00 urn:sha1:d50abd024901176f8b21081713bf4a2779d9aadb Use custom wrap-around type instead of Range 2021-08-22T19:46:03+00:00 Andreas Liljeqvist bonega@gmail.com 2021-08-22T19:46:03+00:00 urn:sha1:5a501f73ff753109c7e73d4981fe011633bd8e84 Fix typos “an”→“a” and a few different ones that appeared in the same search 2021-08-22T16:15:49+00:00 Frank Steffahn frank.steffahn@stu.uni-kiel.de 2021-08-22T16:15:49+00:00 urn:sha1:2f9ddf3bc7cfa79d272b1409be80905be946d831 get rid of incorrect erase_for_fmt 2021-07-16T08:09:56+00:00 Ralf Jung post@ralfj.de 2021-07-16T07:39:35+00:00 urn:sha1:7c720ce6121dd878b25f8e6a645a07563e5a4b01 remove unused error variant 2021-07-14T16:17:50+00:00 Ralf Jung post@ralfj.de 2021-07-14T08:52:08+00:00 urn:sha1:8932aebfdfc8e4be18ed5213ba24f72954c7ba47 consistently treat None-tagged pointers as ints; get rid of some deprecated Scalar methods 2021-07-14T16:17:49+00:00 Ralf Jung post@ralfj.de 2021-07-12T18:29:05+00:00 urn:sha1:626605cea02ee5f512f5efae0cd188ae1a7007c7 CTFE/Miri engine Pointer type overhaul: make Scalar-to-Pointer conversion infallible 2021-07-14T16:17:46+00:00 Ralf Jung post@ralfj.de 2021-07-12T16:22:15+00:00 urn:sha1:d4f7dd670226a4235ea4cf900c14eb9c6a536843 This resolves all the problems we had around "normalizing" the representation of a Scalar in case it carries a Pointer value: we can just use Pointer if we want to have a value taht we are sure is already normalized. Adjust `throw_validation_failure` macro to shorten the use of `with_no_trimmed_paths` 2021-06-14T16:57:53+00:00 Rémy Rakic remy.rakic+github@gmail.com 2021-06-14T16:57:53+00:00 urn:sha1:5af1c725138fddd0a91501ba7a485e5000816ae6