
This round is dependant on https://github.com/rust-lang/llvm-project/pull/101 landing first in rust-lang/rust and won't pass CI until that does. That PR, however, will also break wasm CI because it's changing how the wasm target works. My goal here is to open this early to get it out there so that when that PR lands in rust-lang/rust and CI breaks in stdarch then this can be merged to make CI green again. The changes here are mostly around the codegen for various intrinsics. Some wasm-specific intrinsics have been removed in favor of more general LLVM intrinsics, and other intrinsics have been removed in favor of pattern-matching codegen. The only new instruction supported as part of this chagne is `v128.any_true`. This leaves only one instruction unsupported in LLVM which is `i64x2.abs`. I think the codegen for the instruction is correct in stdsimd, though, and LLVM just needs to update with a pattern-match to actually emit the opcode. That'll happen in a future LLVM update.
core::arch
- Rust's core library architecture-specific intrinsics
The core::arch
module implements architecture-dependent intrinsics (e.g. SIMD).
Usage
core::arch
is available as part of libcore
and it is re-exported by
libstd
. Prefer using it via core::arch
or std::arch
than via this crate.
Unstable features are often available in nightly Rust via the
feature(stdsimd)
.
Using core::arch
via this crate requires nightly Rust, and it can (and does)
break often. The only cases in which you should consider using it via this crate
are:
-
if you need to re-compile
core::arch
yourself, e.g., with particular target-features enabled that are not enabled forlibcore
/libstd
. Note: if you need to re-compile it for a non-standard target, please prefer usingxargo
and re-compilinglibcore
/libstd
as appropriate instead of using this crate. -
using some features that might not be available even behind unstable Rust features. We try to keep these to a minimum. If you need to use some of these features, please open an issue so that we can expose them in nightly Rust and you can use them from there.
Documentation
- Documentation - i686
- Documentation - x86_64
- Documentation - arm
- Documentation - aarch64
- Documentation - powerpc
- Documentation - powerpc64
- How to get started
- How to help implement intrinsics
License
core_arch
is primarily distributed under the terms of both the MIT license and
the Apache License (Version 2.0), with portions covered by various BSD-like
licenses.
See LICENSE-APACHE, and LICENSE-MIT for details.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in core_arch
by you, as defined in the Apache-2.0 license,
shall be dual licensed as above, without any additional terms or conditions.