https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2020-07-28T00:51:13+00:00 2020-07-28T00:51:13+00:00 mark markm@cs.wisc.edu 2020-06-12T02:31:49+00:00 urn:sha1:2c31b45ae878b821975c4ebd94cc1e49f6073fd0 2020-06-18T16:11:15+00:00 Eric Huss eric@huss.org 2020-06-08T16:09:21+00:00 urn:sha1:abb5800dd5b05a1b0b3e1c840866389f05548ed5 2019-08-04T12:50:26+00:00 Ralf Jung post@ralfj.de 2019-04-19T07:37:33+00:00 urn:sha1:5b78e98a372c323c2dfa5a19bc110f1c81415f8e 2019-05-17T14:17:15+00:00 Alex Crichton alex@alexcrichton.com 2019-05-14T21:43:43+00:00 urn:sha1:3c9790e4293e41a1a45a50eaee4e76a1fb64d5f8 This updates to 0.1.13 for `compiler_builtins`, published to fix a few issues. The feature changes here are updated because `compiler_builtins` no longer enables the `c` feature by default but we want to do so through our build still. Closes #60747 Closes #60782 2019-04-10T19:17:31+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2019-04-06T08:37:00+00:00 urn:sha1:81a1121341f4c5af6d224d25757fba0341b62b43 2019-02-02T07:36:03+00:00 Mazdak Farrokhzad twingoow@gmail.com 2019-02-02T07:36:03+00:00 urn:sha1:5594b0d5b8924e57f62d0408acb6d7982e93ad65 2018-12-21T10:33:29+00:00 Ralf Jung post@ralfj.de 2018-12-21T10:33:29+00:00 urn:sha1:3414be0b3eb6192c13865e794817de396eeccd4b 2018-12-14T17:05:31+00:00 Alex Crichton alex@alexcrichton.com 2018-12-14T17:05:31+00:00 urn:sha1:c811915eafb349759d2bba9d7a39a53aef02bb3d This was an accidental regression from #56092, but for `no_std` targets being built and distributed we want to be sure to activate the compiler-builtins `mem` feature which demangles important memory-related intrinsics. 2018-12-12T05:08:22+00:00 Alex Crichton alex@alexcrichton.com 2018-11-20T05:52:50+00:00 urn:sha1:4c21a3bc2afc5933f31f1368f6b3406c5f1bdeb3 Ever since we added a Cargo-based build system for the compiler the standard library has always been a little special, it's never been able to depend on crates.io crates for runtime dependencies. This has been a result of various limitations, namely that Cargo doesn't understand that crates from crates.io depend on libcore, so Cargo tries to build crates before libcore is finished. I had an idea this afternoon, however, which lifts the strategy from #52919 to directly depend on crates.io crates from the standard library. After all is said and done this removes a whopping three submodules that we need to manage! The basic idea here is that for any crate `std` depends on it adds an *optional* dependency on an empty crate on crates.io, in this case named `rustc-std-workspace-core`. This crate is overridden via `[patch]` in this repository to point to a local crate we write, and *that* has a `path` dependency on libcore. Note that all `no_std` crates also depend on `compiler_builtins`, but if we're not using submodules we can publish `compiler_builtins` to crates.io and all crates can depend on it anyway! The basic strategy then looks like: * The standard library (or some transitive dep) decides to depend on a crate `foo`. * The standard library adds ```toml [dependencies] foo = { version = "0.1", features = ['rustc-dep-of-std'] } ``` * The crate `foo` has an optional dependency on `rustc-std-workspace-core` * The crate `foo` has an optional dependency on `compiler_builtins` * The crate `foo` has a feature `rustc-dep-of-std` which activates these crates and any other necessary infrastructure in the crate. A sample commit for `dlmalloc` [turns out to be quite simple][commit]. After that all `no_std` crates should largely build "as is" and still be publishable on crates.io! Notably they should be able to continue to use stable Rust if necessary, since the `rename-dependency` feature of Cargo is soon stabilizing. As a proof of concept, this commit removes the `dlmalloc`, `libcompiler_builtins`, and `libc` submodules from this repository. Long thorns in our side these are now gone for good and we can directly depend on crates.io! It's hoped that in the long term we can bring in other crates as necessary, but for now this is largely intended to simply make it easier to manage these crates and remove submodules. This should be a transparent non-breaking change for all users, but one possible stickler is that this almost for sure breaks out-of-tree `std`-building tools like `xargo` and `cargo-xbuild`. I think it should be relatively easy to get them working, however, as all that's needed is an entry in the `[patch]` section used to build the standard library. Hopefully we can work with these tools to solve this problem! [commit]: https://github.com/alexcrichton/dlmalloc-rs/commit/28ee12db813a3b650a7c25d1c36d2c17dcb88ae3 2018-09-04T19:22:08+00:00 Mark Rousskov mark.simulacrum@gmail.com 2018-08-04T22:24:39+00:00 urn:sha1:9ec5ef541ad17986bfe6ae067a84ea8f7b7ae133