- 13 3月, 2016 11 次提交
-
-
由 Ruud van Asseldonk 提交于
This defines the `_mm256_blendv_pd` and `_mm256_blendv_ps` intrinsics. The `_mm256_blend_pd` and `_mm256_blend_ps` intrinsics are not available as LLVM intrinsics. In Clang they are implemented using the shufflevector builtin. Intel reference: https://software.intel.com/en-us/node/524070.
-
由 Ruud van Asseldonk 提交于
This defines `_mm256_cmp_pd` and `_mm256_cmp_ps`. Intel reference: https://software.intel.com/en-us/node/524075.
-
由 bors 提交于
Call str::to_owned in String::from and uninline it Call str::to_owned in String::from and uninline it These methods were already effectively equal, but now one calls the other, and neither is marked inline. String::from does not need to be inlined, it can be without it just like str::to_owned and String::clone are. Fixes #32163
-
由 Ulrik Sverdrup 提交于
String::from does not need to be inlined, it can be without it just like str::to_owned and String::clone are.
-
由 bors 提交于
Fix name resolution in lexical scopes Currently, `resolve_item_in_lexical_scope` does not check the "ribs" (type parameters and local variables). This can allow items that should be shadowed by type parameters to be named. For example, ```rust struct T { i: i32 } fn f<T>() { let t = T { i: 0 }; // This use of `T` resolves to the struct, not the type parameter } mod Foo { pub fn f() {} } fn g<Foo>() { Foo::f(); // This use of `Foo` resolves to the module, not the type parameter } ``` This PR changes `resolve_item_in_lexical_scope` so that it fails when the item is shadowed by a rib (fixes #32120). This is a [breaking-change], but it looks unlikely to cause breakage in practice. r? @nikomatsakis
-
由 bors 提交于
mk: Fix `make dist` With the movement of the erro-index-generator and rustbook, need to update the rules in `make dist`.
-
由 bors 提交于
Add AVX broadcast and conversion intrinsics This adds the following intrinsics: * `_mm256_broadcast_pd` * `_mm256_broadcast_ps` * `_mm256_cvtepi32_pd` * `_mm256_cvtepi32_ps` * `_mm256_cvtpd_epi32` * `_mm256_cvtpd_ps` * `_mm256_cvtps_epi32` * `_mm256_cvtps_pd` * `_mm256_cvttpd_epi32` * `_mm256_cvttps_epi32` The "avx" codegen feature must be enabled to use these.
-
由 bors 提交于
std: Fix tracking issues and clean deprecated APIs This PR fixes up a number of discrepancies found with tracking issues (some closed, some needed new ones, etc), and also cleans out all pre-1.8 deprecated APIs. The big beast here was dealing with `std::dynamic_lib`, and via many applications of a large hammer it's now out of the standard library.
-
由 Alex Crichton 提交于
Removes all unstable and deprecated APIs prior to the 1.8 release. All APIs that are deprecated in the 1.8 release are sticking around for the rest of this cycle. Some notable changes are: * The `dynamic_lib` module was moved into `rustc_back` as the compiler still relies on a few bits and pieces. * The `DebugTuple` formatter now special-cases an empty struct name with only one field to append a trailing comma.
-
由 Alex Crichton 提交于
With the movement of the erro-index-generator and rustbook, need to update the rules in `make dist`.
-
由 bors 提交于
Statically link run-pass/command-before-exec so it passes not just whenever we happen to bootstrap perfectly.
-
- 12 3月, 2016 29 次提交
-
-
由 bors 提交于
rustdoc: improve crate-local inlining fixes #28537 r? @alexcrichton
-
由 Eduard Burtescu 提交于
Statically link run-pass/command-before-exec so it passes not just whenever we happen to bootstrap perfectly.
-
由 Alex Crichton 提交于
The listed tracking issue was hooked up to the wrong location by accident.
-
由 Alex Crichton 提交于
The referenced issues here were both closed, so hook up a new issue which tracks specifically the prelude traits being unstable.
-
由 Alex Crichton 提交于
These are all insta-stable anyway, so just properly tag them.
-
由 Alex Crichton 提交于
This isn't exported so it doesn't need a tag.
-
由 Alex Crichton 提交于
Don't want to pollute the source tree!
-
由 Alex Crichton 提交于
-
由 bors 提交于
Forbid items with the same name from appearing in overlapping inherent impl blocks For example, the following is now correctly illegal: ```rust struct Foo; impl Foo { fn id() {} } impl Foo { fn id() {} } ``` "Overlapping" here is determined the same way it is for traits (and in fact shares the same code path): roughly, there must be some way of substituting any generic types to unify the impls, such that none of the `where` clauses are provably unsatisfiable under such a unification. Along the way, this PR also introduces an `ImplHeader` abstraction (the first commit) that makes it easier to work with impls abstractly (without caring whether they are trait or inherent impl blocks); see the first commit. Closes #22889 r? @nikomatsakis
-
由 bors 提交于
Rollup of 11 pull requests - Successful merges: #32137, #32158, #32171, #32174, #32178, #32179, #32180, #32181, #32183, #32186, #32197 - Failed merges:
-
由 Manish Goregaokar 提交于
Add FreeBSD amd64 snapshot Snapshot itself: https://github.com/dhuseby/rust-manual-snapshots/pull/3
-
由 Manish Goregaokar 提交于
cleanup int suffixes in libcoretest
-
由 Manish Goregaokar 提交于
Clarify doc for slice slicing (Index impls) Clarify doc for slice slicing (Index impls) This is a follow up for PR #32099 and #32057
-
由 Manish Goregaokar 提交于
removed suffixes for librustc_front
-
由 Manish Goregaokar 提交于
removed integer suffixes in librustc_typeck crate
-
由 Jeffrey Seyfried 提交于
-
由 bors 提交于
cover more linux targets in libstd cargobuild libstd/build.rs checked the target name against `"unknown-linux"`... That doesn't necessarily apply to all Linux targets as some toolchains for embedded targets will change that `unknown` field to some vendor name. Some shifting around was needed since Android is also a Linux target. r? @alexcrichton
-
由 Aaron Turon 提交于
-
由 Manish Goregaokar 提交于
Update getting-started.md In `rustc 1.7.0` the message that is displayed is now `Rust is ready to roll.`
-
由 Manish Goregaokar 提交于
Spell fixes for std::ffi doc comments
-
由 Manish Goregaokar 提交于
Fix a couple compiletest nits.
-
由 Manish Goregaokar 提交于
lint: mark associated types as live for the dead_code pass Associated types of trait impls were being excluded from the live list. So types that only appeared in trait impls were being marked as dead code.
-
由 Manish Goregaokar 提交于
Add missing documentation examples for BinaryHeap. As part of the ongoing effort to document all methods with examples, this commit adds the missing examples for the `BinaryHeap` collection type. This is part of issue #29348. r? @steveklabnik
-
由 Aaron Turon 提交于
-
由 Aaron Turon 提交于
Add regression test for duplicate items in overlapping impls. Note that a regression test already exists for *non*overlapping impls.
-
由 Aaron Turon 提交于
impl blocks. For example, the following is now correctly illegal: ```rust struct Foo; impl Foo { fn id() {} } impl Foo { fn id() {} } ``` "Overlapping" here is determined the same way it is for traits (and in fact shares the same code path): roughly, there must be some way of substituting any generic types to unify the impls, such that none of the `where` clauses are provably unsatisfiable under such a unification. Closes #22889
-
由 Aaron Turon 提交于
This commit introduces the idea of an "impl header", which consists of everything outside the impl body: the Self type, the trait reference (when applicable), and predicates from `where` clauses. This type is usable with the type folding machinery, making it possible to work with impl headers at a higher and more generic level.
-
由 Andrey Cherkashin 提交于
Snapshot itself: https://github.com/dhuseby/rust-manual-snapshots/pull/3
-
由 bors 提交于
Forbid glob-importing from a type alias This PR forbids glob-importing from a type alias or trait (fixes #30560): ```rust type Alias = (); use Alias::*; // This is currently allowed but shouldn't be ``` This is a [breaking-change]. Since the disallowed glob imports don't actually import anything, any breakage can be fixed by removing the offending glob import. r? @alexcrichton
-