https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.52.0 2021-03-17T23:28:09+00:00 2021-03-17T23:28:09+00:00 Dylan DPC dylan.dpc@gmail.com 2021-03-17T23:28:09+00:00 urn:sha1:b688b694d083b94ed19c8c93fb321a52ca98d4d9 Make source-based code coverage compatible with MIR inlining When codegenning code coverage use the instance that coverage data was originally generated for, to ensure basic level of compatibility with MIR inlining. Fixes #83061 2021-03-16T22:42:56+00:00 bors bors@rust-lang.org 2021-03-16T22:42:56+00:00 urn:sha1:e655fb62216b6ba64a094b30f116d7988d19322d Implement (but don't use) valtree and refactor in preparation of use This PR does not cause any functional change. It refactors various things that are needed to make valtrees possible. This refactoring got big enough that I decided I'd want it reviewed as a PR instead of trying to make one huge PR with all the changes. cc `@rust-lang/wg-const-eval` on the following commits: * 2027184 implement valtree * eeecea9 fallible Scalar -> ScalarInt * 042f663 ScalarInt convenience methods cc `@eddyb` on ef04a6d cc `@rust-lang/wg-mir-opt` for cf1700c (`mir::Constant` can now represent either a `ConstValue` or a `ty::Const`, and it is totally possible to have two different representations for the same value) 2021-03-15T22:26:03+00:00 Tomasz Miąsko tomasz.miasko@gmail.com 2021-03-13T00:00:00+00:00 urn:sha1:5a9538acb55f0980728a159996fdeff77b845455 Consider functions to be reachable for code coverage purposes, either when they reach the code generation directly, or indirectly as inlined part of another function. 2021-03-15T16:26:49+00:00 Aaron Hill aa1ronham@gmail.com 2021-03-15T16:26:49+00:00 urn:sha1:e70d47b3b5b9bb8bb680264cee6d88d9c74277bc This query reads from global untracked state, so it always needs to be evaluated. 2021-03-12T12:19:17+00:00 Oli Scherer github35764891676564198441@oli-obk.de 2021-02-22T14:34:23+00:00 urn:sha1:0fe4f38769ff5654cb24a9b84ce69b4cdce46e64 2021-03-12T12:16:14+00:00 Oli Scherer github35764891676564198441@oli-obk.de 2021-02-22T14:09:24+00:00 urn:sha1:a4fbac163e7291b052fa5ec64f14cc0a52932ff4 valtree is a version of constants that is inherently safe to be used within types. This is in contrast to ty::Const which can have different representations of the same value. These representation differences can show up in hashing or equality comparisons, breaking type equality of otherwise equal types. valtrees do not have this problem. 2021-03-09T18:28:01+00:00 Camille GILLOT gillot.camille@gmail.com 2021-01-24T16:14:17+00:00 urn:sha1:38d9d09a58803ebd1f5b4432f9e49d01d2fce0f1 2021-03-09T17:51:37+00:00 Camille GILLOT gillot.camille@gmail.com 2020-11-24T17:12:42+00:00 urn:sha1:1fb257b3b4d11552963103acd8491d1bbea547d0 2021-02-25T21:06:26+00:00 Aaron Hill aa1ronham@gmail.com 2021-02-25T21:06:26+00:00 urn:sha1:42e53ff8adf8a4c7ab8d5f87816e30405a1ec9e2 Fix typo in `param_env_reveal_all_normalized` This made the generated docs look strange: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/context/struct.TyCtxt.html#method.param_env_reveal_all_normalized 2021-02-25T05:41:38+00:00 Joshua Nelson jyn514@gmail.com 2021-02-25T05:41:38+00:00 urn:sha1:0ae4bf912e90bd85d65d52532470ec131ec3bf8a This made the generated docs look strange: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/context/struct.TyCtxt.html#method.param_env_reveal_all_normalized