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

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

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

2022-07-11	rustc_target: Flip the default for `TargetOptions::executables` to true	Vadim Petrochenkov	-1/+1
	Also change `executables` to true for linux-kernel and windows-uwp-gnu targets
2021-09-14	update test	asquared31415	-1/+1

2021-09-14	Fix ICE when `start` lang item has wrong generics	asquared31415	-1/+1

2021-07-08	Do not allow JSON targets to set is-builtin: true	Simonas Kazlauskas	-0/+15

2021-01-13	Update tests for extern block linting	Mark Rousskov	-7/+9

2020-11-23	Rename `optin_builtin_traits` to `auto_traits`	Camelid	-1/+1
	They were originally called "opt-in, built-in traits" (OIBITs), but people realized that the name was too confusing and a mouthful, and so they were renamed to just "auto traits". The feature flag's name wasn't updated, though, so that's what this PR does. There are some other spots in the compiler that still refer to OIBITs, but I don't think changing those now is worth it since they are internal and not particularly relevant to this PR. Also see <https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/opt-in.2C.20built-in.20traits.20(auto.20traits).20feature.20name>.
2020-03-19	Adjust data layout in test	Nikita Popov	-2/+2

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

2018-07-13	Don't silently ignore invalid data in target spec	Jethro Beekman	-1/+1

2018-03-22	rustc: Add a `#[wasm_custom_section]` attribute	Alex Crichton	-0/+75
	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).