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

Age	Commit message (Collapse)	Author	Lines
2018-09-11	stabalize infer outlives requirements (RFC 2093).	toidiu	-1/+0
	Co-authored-by: nikomatsakis
2018-08-24	check that adding infer-outlives requirement to all crates works	Niko Matsakis	-0/+1

2018-08-09	[nll] libprofiler_builtins: enable feature(nll) for bootstrap	memoryruins	-0/+1

2018-07-25	Deny bare_trait_objects globally	Tatsuyuki Ishi	-1/+0

2018-07-12	Deny bare trait objects in the rest of rust	ljedrz	-0/+1

2018-04-07	Inject the `compiler_builtins` crate whenever the `core` crate is injected	Oliver Schneider	-0/+1

2018-03-25	pgo: Blindly try to fix Windows build.	Emilio Cobos Álvarez	-0/+2

2018-03-25	profiler_builtins: Add missing ProfilingNameVar file to the profiler build.	Emilio Cobos Álvarez	-0/+1
	Otherwise opt builds with pgo-gen fail, d'oh. Signed-off-by: Emilio Cobos Álvarez <emilio@crisal.io>
2018-03-25	profiler-builtins: define COMPILER_RT_HAS_UNAME on non-msvc platforms.	Emilio Cobos Álvarez	-0/+1
	Otherwise lprofGetHostName, used by the PGO generator, won't be available. This means that PGO and coverage profiling would be restricted to systems with uname, but that seems acceptable. Signed-off-by: Emilio Cobos Álvarez <emilio@crisal.io>
2017-11-28	*: strip calls to cc::Build::compile	Tamir Duberstein	-1/+1
	The documentation states: "The name output should be the name of the library." and this is already done in more recently-added callers.
2017-10-11	Bump cc to 1.01 to include x86_64-unknown-linux-gnux32 support	Marco A L Barbosa	-1/+1

2017-09-28	Update to the `cc` crate	Alex Crichton	-3/+3
	This is the name the `gcc` crate has moved to
2017-09-02	update gcc crate	Ralf Jung	-1/+1
	Use gcc::Build rather than deprecated gcc::Config. Fixes #43973
2017-08-25	*: remove crate_{name,type} attributes	Tamir Duberstein	-2/+0
	Fixes #41701.
2017-07-25	Bump master to 1.21.0	Alex Crichton	-2/+2
	This commit bumps the master branch's version to 1.21.0 and also updates the bootstrap compiler from the freshly minted beta release.
2017-07-05	Switch to rust-lang-nursery/compiler-builtins	Alex Crichton	-1/+1
	This commit migrates the in-tree `libcompiler_builtins` to the upstream version at https://github.com/rust-lang-nursery/compiler-builtins. The upstream version has a number of intrinsics written in Rust and serves as an in-progress rewrite of compiler-rt into Rust. Additionally it also contains all the existing intrinsics defined in `libcompiler_builtins` for 128-bit integers. It's been the intention since the beginning to make this transition but previously it just lacked the manpower to get done. As this PR likely shows it wasn't a trivial integration! Some highlight changes are: * The PR rust-lang-nursery/compiler-builtins#166 contains a number of fixes across platforms and also some refactorings to make the intrinsics easier to read. The additional testing added there also fixed a number of integration issues when pulling the repository into this tree. * LTO with the compiler-builtins crate was fixed to link in the entire crate after the LTO process as these intrinsics are excluded from LTO. * Treatment of hidden symbols was updated as previously the `#![compiler_builtins]` crate would mark all symbol imports as hidden whereas it was only intended to mark exports as hidden.
2017-06-13	Fix gcc version required by libprofiler_builtins	Marco Castelluccio	-1/+1

2017-06-12	Redefine strdup, open, fdopen as _strdup, _open, _fdopen to avoid linking ↵	Marco Castelluccio	-0/+3
	errors on MSVC
2017-06-12	Compile WindowsMMap too on MSVC	Marco Castelluccio	-14/+15

2017-05-01	Add profiling support, through the rustc -Z profile flag.	whitequark	-0/+94
	When -Z profile is passed, the GCDAProfiling LLVM pass is added to the pipeline, which uses debug information to instrument the IR. After compiling with -Z profile, the $(OUT_DIR)/$(CRATE_NAME).gcno file is created, containing initial profiling information. After running the program built, the $(OUT_DIR)/$(CRATE_NAME).gcda file is created, containing branch counters. The created .gcno and .gcda files can be processed using the "llvm-cov gcov" and "lcov" tools. The profiling data LLVM generates does not faithfully follow the GCC's format for .gcno and .gcda files, and so it will probably not work with other tools (such as gcov itself) that consume these files.