https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.61.0 2022-03-10T16:16:33+00:00 2022-03-10T16:16:33+00:00 Augie Fackler augie@google.com 2022-03-10T16:16:33+00:00 urn:sha1:185e3b95ca198ec10e6777d31e2c8d92c43f2ce2 This is required after LLVM change 3c4410dfcaaf (aka https://reviews.llvm.org/D121168) did some includes cleanup. 2022-03-02T23:28:50+00:00 Tomasz Miąsko tomasz.miasko@gmail.com 2022-03-03T00:00:00+00:00 urn:sha1:926bf1a3718fc408b2d75a7536b7a2ed3d2d070b 2022-03-02T08:48:33+00:00 bors bors@rust-lang.org 2022-03-02T08:48:33+00:00 urn:sha1:c42d846add941a26bd254911e16f02c4a3f9346f Remove LLVM attribute removal This was necessary before, because `declare_raw_fn` would always apply the default optimization attributes to every declared function. Then `attributes::from_fn_attrs` would have to remove the default attributes in the case of, e.g. `#[optimize(speed)]` in a `-Os` build. (see [`src/test/codegen/optimize-attr-1.rs`](https://github.com/rust-lang/rust/blob/03a8cc7df1d65554a4d40825b0490c93ac0f0236/src/test/codegen/optimize-attr-1.rs#L33)) However, every relevant callsite of `declare_raw_fn` (i.e. where we actually generate code for the function, and not e.g. a call to an intrinsic, where optimization attributes don't [?] matter) calls `from_fn_attrs`, so we can remove the attribute setting from `declare_raw_fn`, and rely on `from_fn_attrs` to apply the correct attributes all at once. r? `@ghost` (blocked on #94221) `@rustbot` label S-blocked 2022-02-28T05:02:11+00:00 Erik Desjardins erikdesjardins@users.noreply.github.com 2022-02-21T19:47:56+00:00 urn:sha1:dce14cfacc232e80dbed68430183085fd39dea02 This was necessary before, because `declare_raw_fn` would always apply the default optimization attributes to every declared function, and then `attributes::from_fn_attrs` would have to remove the default attributes in the case of, e.g. `#[optimize(speed)]` in a `-Os` build. However, every relevant callsite of `declare_raw_fn` (i.e. where we actually generate code for the function, and not e.g. a call to an intrinsic, where optimization attributes don't [?] matter) calls `from_fn_attrs`, so we can simply remove the attribute setting from `declare_raw_fn`, and rely on `from_fn_attrs` to apply the correct attributes all at once. 2022-02-28T04:11:03+00:00 Erik Desjardins erikdesjardins@users.noreply.github.com 2022-02-26T17:52:07+00:00 urn:sha1:851fcc7a54262748b1aa9e16de91453998d896f3 This reverts commit 4f49627c6fe2a32d1fed6310466bb0e1c535c0c0, reversing changes made to 028c6f1454787c068ff5117e9000a1de4fd98374. 2022-02-26T22:16:01+00:00 Erik Desjardins erikdesjardins@users.noreply.github.com 2022-02-26T22:16:01+00:00 urn:sha1:0d0cc4f6a0cb48600f183c382986df1897bdb7dc 2022-02-26T21:58:45+00:00 Erik Desjardins erikdesjardins@users.noreply.github.com 2022-02-26T21:58:45+00:00 urn:sha1:ac9f4f7d0de3986246a19678919ff15252870b15 2022-02-26T18:14:55+00:00 Erik Desjardins erikdesjardins@users.noreply.github.com 2022-02-21T16:19:16+00:00 urn:sha1:30d3ce06742fc5d0eb844239652a0af4d47bb095 This should improve performance. 2022-02-18T22:23:03+00:00 Matthias Krüger matthias.krueger@famsik.de 2022-02-18T22:23:03+00:00 urn:sha1:0bb72a2c66d0daa417baa27eaf2d276d835b87a2 Add MemTagSanitizer Support Add support for the LLVM [MemTagSanitizer](https://llvm.org/docs/MemTagSanitizer.html). On hardware which supports it (see caveats below), the MemTagSanitizer can catch bugs similar to AddressSanitizer and HardwareAddressSanitizer, but with lower overhead. On a tag mismatch, a SIGSEGV is signaled with code SEGV_MTESERR / SEGV_MTEAERR. # Usage `-Zsanitizer=memtag -C target-feature="+mte"` # Comments/Caveats * MemTagSanitizer is only supported on AArch64 targets with hardware support * Requires `-C target-feature="+mte"` * LLVM MemTagSanitizer currently only performs stack tagging. # TODO * Tests * Example 2022-02-16T14:39:03+00:00 Ivan Lozano ivanlozano@google.com 2021-12-03T21:11:13+00:00 urn:sha1:568aeda9e955ca2a4c043bc2ae7f854e60f6103a Adds support for the LLVM MemTagSanitizer.