rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2019-04-15	Preallocate BUILTIN_ATTRIBUTES symbols and use a hash map instead of looping	John Kåre Alsaker	-0/+2

2019-02-26	update scoped_tls to 1.0	Marcel Hellwig	-1/+1

2019-02-13	Rename rustc_errors dependency in rust 2018 crates	Taiki Endo	-1/+1

2019-02-07	libsyntax => 2018	Taiki Endo	-0/+1

2018-12-10	Upgrade `smallvec` to 0.6.7 and use the new `may_dangle` feature.	Nicholas Nethercote	-1/+1

2018-08-23	Use optimized SmallVec implementation	Igor Gutorov	-0/+1

2018-04-26	rustc_target: move in syntax::abi and flip dependency.	Irina Popa	-1/+1

2018-03-14	Remove syntax and syntax_pos thread locals	John Kåre Alsaker	-0/+1

2018-01-07	Try to fix a perf regression by updating log	Malo Jaffré	-1/+1
	Upgrade `log` to `0.4` in multiple crates.
2017-09-17	Remove rustc_bitflags; use the bitflags crate	Tamir Duberstein	-1/+2

2017-05-07	fix the easy features in libsyntax	ubsan	-1/+1

2017-03-23	Remove internal liblog	Alex Crichton	-1/+1
	This commit deletes the internal liblog in favor of the implementation that lives on crates.io. Similarly it's also setting a convention for adding crates to the compiler. The main restriction right now is that we want compiler implementation details to be unreachable from normal Rust code (e.g. requires a feature), and by default everything in the sysroot is reachable via `extern crate`. The proposal here is to require that crates pulled in have these lines in their `src/lib.rs`: #![cfg_attr(rustbuild, feature(staged_api, rustc_private))] #![cfg_attr(rustbuild, unstable(feature = "rustc_private", issue = "27812"))] This'll mean that by default they're not using these attributes but when compiled as part of the compiler they do a few things: * Mark themselves as entirely unstable via the `staged_api` feature and the `#![unstable]` attribute. * Allow usage of other unstable crates via `feature(rustc_private)` which is required if the crate relies on any other crates to compile (other than std).
2017-02-03	Bump version, upgrade bootstrap	Alex Crichton	-1/+0
	This commit updates the version number to 1.17.0 as we're not on that version of the nightly compiler, and at the same time this updates src/stage0.txt to bootstrap from freshly minted beta compiler and beta Cargo.
2016-12-30	Such large. Very 128. Much bits.	Simonas Kazlauskas	-0/+1
	This commit introduces 128-bit integers. Stage 2 builds and produces a working compiler which understands and supports 128-bit integers throughout. The general strategy used is to have rustc_i128 module which provides aliases for iu128, equal to iu64 in stage9 and iu128 later. Since nowhere in rustc we rely on large numbers being supported, this strategy is good enough to get past the first bootstrap stages to end up with a fully working 128-bit capable compiler. In order for this strategy to work, number of locations had to be changed to use associated max_value/min_value instead of MAX/MIN constants as well as the min_value (or was it max_value?) had to be changed to use xor instead of shift so both 64-bit and 128-bit based consteval works (former not necessarily producing the right results in stage1). This commit includes manual merge conflict resolution changes from a rebase by @est31.
2016-11-11	Change implementation of syntax::util::SmallVector to use ↵	Mark-Simulacrum	-0/+1
	data_structures::SmallVec.
2016-06-27	Fix `Cargo.toml`s	Jeffrey Seyfried	-1/+2

2016-06-23	Move errors from libsyntax to its own crate	Jonathan Turner	-0/+1

2016-04-01	rustbuild: Fix dist for non-host targets	Alex Crichton	-1/+0
	The `rust-std` package that we produce is expected to have not only the standard library but also libtest for compiling unit tests. Unfortunately this does not currently happen due to the way rustbuild is structured. There are currently two main stages of compilation in rustbuild, one for the standard library and one for the compiler. This is primarily done to allow us to fill in the sysroot right after the standard library has finished compiling to continue compiling the rest of the crates. Consequently the entire compiler does not have to explicitly depend on the standard library, and this also should allow us to pull in crates.io dependencies into the build in the future because they'll just naturally build against the std we just produced. These phases, however, do not represent a cross-compiled build. Target-only builds also require libtest, and libtest is currently part of the all-encompassing "compiler build". There's unfortunately no way to learn about just libtest and its dependencies (in a great and robust fashion) so to ensure that we can copy the right artifacts over this commit introduces a new build step, libtest. The new libtest build step has documentation, dist, and link steps as std/rustc already do. The compiler now depends on libtest instead of libstd, and all compiler crates can now assume that test and its dependencies are implicitly part of the sysroot (hence explicit dependencies being removed). This makes the build a tad less parallel as in theory many rustc crates can be compiled in parallel with libtest, but this likely isn't where we really need parallelism either (all the time is still spent in the compiler). All in all this allows the `dist-std` step to depend on both libstd and libtest, so `rust-std` packages produced by rustbuild should start having both the standard library and libtest. Closes #32523
2016-02-21	rustbuild: Sync some Cargo.toml/lib.rs dependencies	Alex Crichton	-2/+1
	The standard library doesn't depend on rustc_bitflags, so move it to explicit dependencies on all other crates. Additionally, the arena/fmt_macros deps could be dropped from libsyntax.
2016-02-11	bootstrap: Add a bunch of Cargo.toml files	Alex Crichton	-0/+16
	These describe the structure of all our crate dependencies.