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

Age	Commit message (Collapse)	Author	Lines
2022-04-03	Cleanup after some refactoring in rustc_target	Loïc BRANSTETT	-2/+4

2022-03-26	Merge commit '39683d8eb7a32a74bea96ecbf1e87675d3338506' into ↵	bjorn3	-6/+29
	sync_cg_gcc-2022-03-26
2022-03-02	rename ErrorReported -> ErrorGuaranteed	mark	-3/+3

2022-03-01	Querify `global_backend_features`	Simonas Kazlauskas	-1/+1
	At the very least this serves to deduplicate the diagnostics that are output about unknown target features provided via CLI.
2021-12-31	Remove unused extern crate rustc_symbol_mangling	bjorn3	-1/+0

2021-12-31	Merge commit '1411a98352ba6bee8ba3b0131c9243e5db1e6a2e' into ↵	bjorn3	-2/+0
	sync_cg_clif-2021-12-31
2021-12-13	Use `OutputFilenames` to generate output file for `-Zllvm-time-trace`	Tomasz Miąsko	-1/+1
	The resulting profile will include the crate name and will be stored in the `--out-dir` directory. This implementation makes it convenient to use LLVM time trace together with cargo, in the contrast to the previous implementation which would overwrite profiles or store them in `.cargo/registry/..`.
2021-12-07	Use object crate for .rustc metadata generation	Nikita Popov	-5/+0
	We already use the object crate for generating uncompressed .rmeta metadata object files. This switches the generation of compressed .rustc object files to use the object crate as well. These have slightly different requirements in that .rmeta should be completely excluded from any final compilation artifacts, while .rustc should be part of shared objects, but not loaded into memory. The primary motivation for this change is #90326: In LLVM 14, the current way of setting section flags (and in particular, preventing the setting of SHF_ALLOC) will no longer work. There are other ways we could work around this, but switching to the object crate seems like the most elegant, as we already use it for .rmeta, and as it makes this independent of the codegen backend. In particular, we don't need separate handling in codegen_llvm and codegen_gcc. codegen_cranelift should be able to reuse the implementation as well, though I have omitted that here, as it is not based on codegen_ssa. This change mostly extracts the existing code for .rmeta handling to allow using it for .rustc as well, and adjust the codegen infrastructure to handle the metadata object file separately: We no longer create a backend-specific module for it, and directly produce the compiled module instead. This does not fix #90326 by itself yet, as .llvmbc will need to be handled separately.
2021-09-30	Rebase fallout.	Camille GILLOT	-1/+1

2021-09-28	Merge commit '9809f5d21990d9e24b3e9876ea7da756fd4e9def' into libgccjit-codegen	Antoni Boucher	-23/+4

2021-09-17	Merge commit '48d60ab7c505c6c1ebb042eacaafd8dc9f7a9267' into libgccjit-codegen	Antoni Boucher	-3/+2

2021-08-15	Merge commit 'e228f0c16ea8c34794a6285bf57aab627c26b147' into libgccjit-codegen	Antoni Boucher	-39/+10

2021-08-12	Add 'compiler/rustc_codegen_gcc/' from commit ↵	Antoni Boucher	-0/+342
	'afae271d5d3719eeb92c18bc004bb6d1965a5f3f' git-subtree-dir: compiler/rustc_codegen_gcc git-subtree-mainline: ae90dcf0207c57c3034f00b07048d63f8b2363c8 git-subtree-split: afae271d5d3719eeb92c18bc004bb6d1965a5f3f