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

Age	Commit message (Collapse)	Author	Lines
2023-11-19	Pass TyCtxt by value	Antoni Boucher	-1/+1

2023-11-19	Merge commit '2e8386e9fb3506cef991d04f8b3bc78f9a0c2630' into ↵	Antoni Boucher	-9/+7
	subtree-update_cg_gcc_2023-11-17
2023-10-26	Merge commit 'e4fe941b11a55c5005630696e9b6d81c65f7bd04' into ↵	Antoni Boucher	-3/+4
	subtree-update_cg_gcc_2023-10-25
2023-10-09	Fix checks	Antoni Boucher	-1/+1

2023-10-09	Merge commit '11a0cceab966e5ff1058ddbcab5977e8a1d6d290' into ↵	Antoni Boucher	-28/+43
	subtree-update_cg_gcc_2023-10-09
2023-07-17	Introduce `MonoItemData`.	Nicholas Nethercote	-2/+2
	It replaces `(Linkage, Visibility)`, making the code nicer. Plus the next commit will add another field.
2023-03-05	Merge commit '08a6d6e16b5efe217123e780398969946266268f' into ↵	Antoni Boucher	-4/+41
	sync-cg_gcc-2023-03-04
2022-12-20	rustc: Remove needless lifetimes	Jeremy Stucki	-1/+1

2022-07-13	Rename `debugging_opts` to `unstable_opts`	Joshua Nelson	-1/+1
	This is no longer used only for debugging options (e.g. `-Zoutput-width`, `-Zallow-features`). Rename it to be more clear.
2022-06-06	Merge commit 'e8dca3e87d164d2806098c462c6ce41301341f68' into sync_from_cg_gcc	Antoni Boucher	-0/+10

2022-03-26	Merge commit '39683d8eb7a32a74bea96ecbf1e87675d3338506' into ↵	bjorn3	-4/+13
	sync_cg_gcc-2022-03-26
2021-12-31	Merge commit '1411a98352ba6bee8ba3b0131c9243e5db1e6a2e' into ↵	bjorn3	-0/+3
	sync_cg_clif-2021-12-31
2021-12-07	Use object crate for .rustc metadata generation	Nikita Popov	-39/+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-10-20	Make hash_result an Option.	Camille GILLOT	-1/+7

2021-09-30	Rebase fallout.	Camille GILLOT	-2/+2

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

2021-08-15	Merge commit 'e228f0c16ea8c34794a6285bf57aab627c26b147' into libgccjit-codegen	Antoni Boucher	-7/+12

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