https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.25.0 2018-01-20T09:55:16+00:00 2018-01-20T09:55:16+00:00 Simon Sapin simon.sapin@exyr.org 2017-12-22T18:12:22+00:00 urn:sha1:fb03a49c2501c52401b3c987fd455818de1736f2 2017-12-09T22:18:33+00:00 Matt Brubeck mbrubeck@limpet.net 2017-12-09T01:32:04+00:00 urn:sha1:3024c1434a667425d30e4b0785857381323712aa 2017-10-20T19:29:35+00:00 steveklabnik steve@steveklabnik.com 2017-10-20T19:29:35+00:00 urn:sha1:f8f9005e57852d4775b952d3b430e458a6a414bb 2017-08-29T00:58:17+00:00 bors bors@rust-lang.org 2017-08-29T00:58:17+00:00 urn:sha1:d2d50691aadfb9e25c8c3d9a1d71a8c79607c5b2 std: Mark allocation functions as nounwind This commit flags all allocation-related functions in liballoc as "this can't unwind" which should largely resolve the size-related issues found on #42808. The documentation on the trait was updated with such a restriction (they can't panic) as well as some other words about the relative instability about implementing a bullet-proof allocator. Closes #42808 2017-08-28T15:06:52+00:00 Alex Crichton alex@alexcrichton.com 2017-08-22T21:36:49+00:00 urn:sha1:b6f554b6dc972608761db93a375bcb0e89155e1d This commit flags all allocation-related functions in liballoc as "this can't unwind" which should largely resolve the size-related issues found on #42808. The documentation on the trait was updated with such a restriction (they can't panic) as well as some other words about the relative instability about implementing a bullet-proof allocator. Closes #42808 2017-08-24T16:42:53+00:00 lukaramu lukaramu@users.noreply.github.com 2017-08-24T15:33:36+00:00 urn:sha1:49ee9f3f08ba4583bc722a663e43551067ace271 This fixes headings reading "Unsafety" and "Example", they should be "Safety" and "Examples" according to RFC 1574. 2017-08-15T19:56:30+00:00 Fourchaux jprodi04@gmail.com 2017-08-15T19:45:21+00:00 urn:sha1:c7104be1a37daa2f7ec114913247dc93524fd48e 2017-08-13T19:28:57+00:00 bors bors@rust-lang.org 2017-08-13T19:28:57+00:00 urn:sha1:ab40a7cb0e01159a04d4cfffc432c6d77f1f23c8 Optimize allocation paths in RawVec Since the `Alloc` trait was introduced (https://github.com/rust-lang/rust/pull/42313) and it was integrated everywhere (https://github.com/rust-lang/rust/pull/42727) there's been some slowdowns and regressions that have slipped through. The intention of this PR is to try to tackle at least some of them, but they've been very difficult to quantify up to this point so it probably doesn't solve everything. This PR primarily targets the `RawVec` type, specifically the `double` function. The codegen for this function is now much closer to what it was before #42313 landed as many runtime checks have been elided. 2017-08-12T12:01:11+00:00 Bastien Orivel eijebong@bananium.fr 2017-08-11T18:34:14+00:00 urn:sha1:3ab86fbab281ca059731c31fa2aee5d9afc7e6dc 2017-08-11T22:58:26+00:00 Alex Crichton alex@alexcrichton.com 2017-08-11T22:58:26+00:00 urn:sha1:a83d2afbba772f474872aacc6c21f2b5270fc517 None of these require a significant amount of code and using `#[inline]` will allow constructors to get inlined, improving codegen at allocation callsites.