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

Age	Commit message (Collapse)	Author	Lines
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.