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

Age	Commit message (Collapse)	Author	Lines
2019-09-26	hir: Disallow `target_feature` on constants	David Wood	-50/+0
	This commit fixes an ICE when `target_feature` is applied to constants. Signed-off-by: David Wood <david@davidtw.co>
2019-07-07	normalize use of backticks in compiler messages for librustc_typecheck	Samy Kacimi	-2/+2
	https://github.com/rust-lang/rust/issues/60532
2019-05-25	Reword malformed attribute input diagnostics	Esteban Küber	-14/+17
	- Handle empty `cfg_attr` attribute - Reword empty `derive` attribute error - Use consistend error message: "malformed `attrname` attribute input" - Provide suggestions when possible - Move note/help to label/suggestion - Use consistent wording "ill-formed" -> "malformed" - Move diagnostic logic out of parser
2019-03-11	Update tests	Vadim Petrochenkov	-1/+1

2019-01-13	Implement basic input validation for built-in attributes	Vadim Petrochenkov	-1/+1

2018-12-25	Remove licenses	Mark Rousskov	-7/+7

2018-07-31	tests/ui: Add missing mips{64} ignores	dragan.mladjenovic	-7/+7

2018-06-17	test: Ignore some problematic tests on powerpc and powerpc64*	John Paul Adrian Glaubitz	-7/+7

2018-06-04	test: Ignore some problematic tests on sparc and sparc64	John Paul Adrian Glaubitz	-7/+7

2018-04-16	Separately gate each target_feature feature	Alex Crichton	-2/+2
	Use an explicit whitelist for what features are actually stable and can be enabled.
2018-04-10	Add ignores for powerpc and s390x to target-feature-wrong.rs and update ↵	dragan.mladjenovic	-7/+7
	references.
2018-04-10	Update ui test references.	dragan.mladjenovic	-6/+6

2018-03-27	rustc: Forbid #[inline(always)] with #[target_feature]	Alex Crichton	-1/+7
	Once a target feature is enabled for a function that means that it in general can't be inlined into other functions which don't have that target feature enabled. This can cause both safety and LLVM issues if we were to actually inline it, so `#[inline(always)]` both can't be respected and would be an error if we did so! Today LLVM doesn't inline functions with different `#[target_feature]` annotations, but it turns out that if one is tagged with `#[inline(always)]` it'll override this and cause scary LLVM error to arise! This commit fixes this issue by forbidding these two attributes to be used in conjunction with one another. cc rust-lang-nursery/stdsimd#404
2018-03-07	rustc: Fix ICE with `#[target_feature]` on module	Alex Crichton	-1/+10
	This commit fixes an ICE in rustc when `#[target_feature]` was applied to items other than functions due to the way the feature was validated.
2018-02-26	Update UI tests	Vadim Petrochenkov	-5/+5

2018-01-13	rustc: Refactor attribute checking to operate on HIR	Alex Crichton	-10/+10
	This'll enable running queries that could be cached and overall be more amenable to the query infastructure.
2018-01-13	rustc: Tweak `#[target_feature]` syntax	Alex Crichton	-0/+32
	This is an implementation of the `#[target_feature]` syntax-related changes of [RFC 2045][rfc]. Notably two changes have been implemented: * The new syntax is `#[target_feature(enable = "..")]` instead of `#[target_feature = "+.."]`. The `enable` key is necessary instead of the `+` to indicate that a feature is being enabled, and a sub-list is used for possible expansion in the future. Additionally within this syntax the feature names being enabled are now whitelisted against a known set of target feature names that we know about. * The `#[target_feature]` attribute can only be applied to unsafe functions. It was decided in the RFC that invoking an instruction possibly not defined for the current processor is undefined behavior, so to enable this feature for now it requires an `unsafe` intervention. [rfc]: https://github.com/rust-lang/rfcs/blob/master/text/2045-target-feature.md