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

Age	Commit message (Collapse)	Author	Lines
2023-01-11	Move /src/test to /tests	Albert Larsan	-515/+0

2022-12-31	Add missing extern crate rustc_driver	bjorn3	-0/+5

2022-08-23	Diagnose missing includes in run-make tests	Tomasz Miąsko	-1/+1

2022-08-07	Remove even more box syntax uses from src/test	est31	-8/+7
	Prior work, notably 6550021124451628b1efc60c59284465b109e3aa from #88316 has removed box syntax from most of the testsuite. However, some tests were left out. This commit removes box_syntax uses from more locations in src/test. Some tests that are very box syntax specific are not being migrated.
2021-06-04	Remove `doc(include)`	Joshua Nelson	-4/+3

2020-08-14	Fix run-make test	Matthew Jasper	-56/+60

2020-06-03	Update fulldeps tests and clippy	Vadim Petrochenkov	-2/+2

2020-06-02	Rename the crates in source code	Vadim Petrochenkov	-2/+2

2019-07-31	Remove derives `Encodable`/`Decodable` and unstabilize attribute `#[bench]`	Vadim Petrochenkov	-2/+3

2018-12-25	Remove licenses	Mark Rousskov	-50/+0

2018-03-22	rustc: Add a `#[wasm_custom_section]` attribute	Alex Crichton	-0/+557
	This commit is an implementation of adding custom sections to wasm artifacts in rustc. The intention here is to expose the ability of the wasm binary format to contain custom sections with arbitrary user-defined data. Currently neither our version of LLVM nor LLD supports this so the implementation is currently custom to rustc itself. The implementation here is to attach a `#[wasm_custom_section = "foo"]` attribute to any `const` which has a type like `[u8; N]`. Other types of constants aren't supported yet but may be added one day! This should hopefully be enough to get off the ground with some custom section support. The current semantics are that any constant tagged with `#[wasm_custom_section]` section will be appended to the corresponding section in the final output wasm artifact (and this affects dependencies linked in as well, not just the final crate). This means that whatever is interpreting the contents must be able to interpret binary-concatenated sections (or each constant needs to be in its own custom section). To test this change the existing `run-make` test suite was moved to a `run-make-fulldeps` folder and a new `run-make` test suite was added which applies to all targets by default. This test suite currently only has one test which only runs for the wasm target (using a node.js script to use `WebAssembly` in JS to parse the wasm output).