https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.20.0 2017-07-05T21:37:01+00:00 2017-07-05T21:37:01+00:00 Alex Crichton alex@alexcrichton.com 2017-06-03T21:54:08+00:00 urn:sha1:695dee063bcd40f154bb27b7beafcb3d4dd775ac This PR is an implementation of [RFC 1974] which specifies a new method of defining a global allocator for a program. This obsoletes the old `#![allocator]` attribute and also removes support for it. [RFC 1974]: https://github.com/rust-lang/rfcs/pull/197 The new `#[global_allocator]` attribute solves many issues encountered with the `#![allocator]` attribute such as composition and restrictions on the crate graph itself. The compiler now has much more control over the ABI of the allocator and how it's implemented, allowing much more freedom in terms of how this feature is implemented. cc #27389 2017-04-15T16:01:56+00:00 Matt Brubeck mbrubeck@limpet.net 2017-03-10T01:53:01+00:00 urn:sha1:675475c4d3e3b1ebff5b761570f4a3f9a0ca23df Fixes #38723. 2017-04-08T20:28:32+00:00 Shiz hi@shiz.me 2017-04-08T18:36:00+00:00 urn:sha1:536011d929ecbd1170baf34e09580e567c971f95 Just like DragonFlyBSD, using the same symbols as the system allocator will result in a segmentation fault at runtime due to allocator mismatches. As such, prefix the jemalloc symbols instead. 2017-03-12T18:59:04+00:00 Corey Farwell coreyf@rwell.org 2017-03-12T18:13:35+00:00 urn:sha1:97a1b6a055d69cf21faa9773133725bdfddc5196 As of last year with version 'Sierra', the Mac operating system is now called 'macOS'. 2017-02-21T19:38:17+00:00 Alex Crichton alex@alexcrichton.com 2017-02-15T16:53:18+00:00 urn:sha1:40aaa65734d72b7aabda3cd0925b0119fb6d5a0a As we continue to add more crates to the compiler and use them to implement various features we want to be sure we're not accidentally expanding the API surface area of the compiler! To that end this commit adds a new `run-make` test which will attempt to `extern crate foo` all crates in the sysroot, verifying that they're all unstable. This commit discovered that the `std_shim` and `test_shim` crates were accidentally stable and fixes the situation by deleting those shims. The shims are no longer necessary due to changes in Cargo that have happened since they were originally incepted. 2017-02-06T16:42:54+00:00 Alex Crichton alex@alexcrichton.com 2017-01-23T23:55:35+00:00 urn:sha1:77c3bfa7429abf87b76ba84108df018d9e9d90e2 These are all now no longer needed that we've only got rustbuild in tree. 2017-01-27T07:47:39+00:00 Alex Crichton alex@alexcrichton.com 2017-01-22T20:53:35+00:00 urn:sha1:a5561ce2b94c33add47d288e1826183c511ec9fa This hides symbols from various unstable and implementation-detail crates of the standard library. Although typically transitive exported `pub extern` functions are exported from cdylibs, these crates aren't necessary as they're all implementation details. Closes #34493 2017-01-08T08:22:06+00:00 bors bors@rust-lang.org 2017-01-08T08:22:06+00:00 urn:sha1:7ac9d337dcc544b4b1959997cdd36f1ba0c8d3e1 Remove not(stage0) from deny(warnings) Historically this was done to accommodate bugs in lints, but there hasn't been a bug in a lint since this feature was added which the warnings affected. Let's completely purge warnings from all our stages by denying warnings in all stages. This will also assist in tracking down `stage0` code to be removed whenever we're updating the bootstrap compiler. 2016-12-30T05:07:20+00:00 Alex Crichton alex@alexcrichton.com 2016-12-29T17:47:34+00:00 urn:sha1:9b0b5b45dbd268aba0a79453f506bfe00bb57042 Historically this was done to accommodate bugs in lints, but there hasn't been a bug in a lint since this feature was added which the warnings affected. Let's completely purge warnings from all our stages by denying warnings in all stages. This will also assist in tracking down `stage0` code to be removed whenever we're updating the bootstrap compiler. 2016-12-30T02:30:01+00:00 Jonathan A. Kollasch jakllsch@kollasch.net 2016-12-06T21:55:11+00:00 urn:sha1:5672c9b606826ba83a1b96cdad198d4add6dbd3d