about summary refs log tree commit diff
path: root/src/test/compile-fail/feature-gate-simd-ffi.rs
AgeCommit message (Collapse)AuthorLines
2017-12-07Migrate a few feature gate tests to uiest31-24/+0
Renames only in this commit, and obviously .stderr file additions.
2015-12-10std: Remove deprecated functionality from 1.5Alex Crichton-8/+6
This is a standard "clean out libstd" commit which removes all 1.5-and-before deprecated functionality as it's now all been deprecated for at least one entire cycle.
2015-08-17Fix existing tests for new `#[repr(simd)]`.Huon Wilson-3/+3
2015-06-17Fallout in tests and docs from feature renamingsAlex Crichton-1/+1
2015-04-01Fallout in testsNiko Matsakis-1/+1
2015-02-11rustc: Fix a number of stability lint holesAlex Crichton-1/+1
There are a number of holes that the stability lint did not previously cover, including: * Types * Bounds on type parameters on functions and impls * Where clauses * Imports * Patterns (structs and enums) These holes have all been fixed by overriding the `visit_path` function on the AST visitor instead of a few specialized cases. This change also necessitated a few stability changes: * The `collections::fmt` module is now stable (it was already supposed to be). * The `thread_local::imp::Key` type is now stable (it was already supposed to be). * The `std::rt::{begin_unwind, begin_unwind_fmt}` functions are now stable. These are required via the `panic!` macro. * The `std::old_io::stdio::{println, println_args}` functions are now stable. These are required by the `print!` and `println!` macros. * The `ops::{FnOnce, FnMut, Fn}` traits are now `#[stable]`. This is required to make bounds with these traits stable. Note that manual implementations of these traits are still gated by default, this stability only allows bounds such as `F: FnOnce()`. Additionally, the compiler now has special logic to ignore its own generated `__test` module for the `--test` harness in terms of stability. Closes #8962 Closes #16360 Closes #20327 [breaking-change]
2015-01-17Feature gate SIMD in FFI, due to unknown ABIs.Huon Wilson-0/+26
I don't know if this handling of SIMD types is correct for the C ABI on all platforms, so lets add an even finer feature gate than just the `simd` one. The `simd` one can be used with (relatively) little risk of complete nonsense, the reason for it is that it is likely that things will change. Using the types in FFI with an incorrect ABI will at best give absolute nonsense results, but possibly cause serious breakage too, so this is a step up in badness, hence a new feature gate.