rust/src/test/ui/simd, branch 1.56.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.56.02021-08-30T09:00:21+00:00`feature(const_generics)` -> `feature(const_param_types)`2021-08-30T09:00:21+00:00lcnrrust@lcnr.de2021-08-27T16:04:57+00:00urn:sha1:0c28e028b6f45f33447f24de7dd762b8599b7a4eAllow generic SIMD array element type2021-08-03T03:33:09+00:00Caleb Zulawskicaleb.zulawski@gmail.com2021-08-03T03:33:09+00:00urn:sha1:b23de51dcbd8f50094a716c0d99b44fdfa68e474std: Stabilize wasm simd intrinsics2021-06-11T02:42:05+00:00Alex Crichtonalex@alexcrichton.com2021-06-10T14:11:23+00:00urn:sha1:e05bb26d9fdcfe69e9a6d225fe1b3ce07b7ffefd
This commit performs two changes to stabilize Rust support for
WebAssembly simd intrinsics:
* The stdarch submodule is updated to pull in rust-lang/stdarch#1179.
* The `wasm_target_feature` feature gate requirement for the `simd128`
feature has been removed, stabilizing the name `simd128`.
This should conclude the FCP started on #74372 and...
Closes #74372
Auto merge of #85919 - workingjubilee:simd-ptrs-are-valid, r=petrochenkov2021-06-05T06:17:17+00:00borsbors@rust-lang.org2021-06-05T06:17:17+00:00urn:sha1:4e20754629c2ee51760d2d5ab3abb09d3e994e8a
Allow raw pointers in SIMD types
Closes #85915 by loosening the strictness in typechecking and adding a test to guarantee it passes.
This still might be too strict, as references currently do pass monomorphization, but my understanding is that they are not guaranteed to be "scalar" in the same way.
wasm: Make simd types passed via indirection again2021-06-03T16:55:45+00:00Alex Crichtonalex@alexcrichton.com2021-06-03T15:58:12+00:00urn:sha1:55769a5ca98452967deb66dc1043a45fe0b2ddba
This commit updates wasm target specs to use `simd_types_indirect: true`
again. Long ago this was added since wasm simd types were always
translated to `v128` under-the-hood in LLVM, meaning that it didn't
matter whether that target feature was enabled or not. Now, however,
`v128` is conditionally used in codegen depending on target features
enabled, meaning that it's possible to get linker errors about different
signatures in code that correctly uses simd types. The fix is the same
as for all other platforms, which is to pass the type indirectly.
test for more SIMD monomorphization errors2021-06-02T22:47:15+00:00Jacob Lifshayprogrammerjake@gmail.com2021-06-02T22:47:15+00:00urn:sha1:d9a5df669c45204daa5e10f5221ff82026fef9e6
build-fail test for simd type with an element type that's a wide pointer
test for SIMD element type of optional nonnull ptr to extern type
test that wide ptr simd element type of *mut [u8] failsAllow raw pointers in SIMD types2021-06-02T00:00:44+00:00Jubilee Youngworkingjubilee@gmail.com2021-06-01T23:43:48+00:00urn:sha1:d03683caf66082e0430db5d07e67e82c5b7d676fTest THIR unsafeck for unsafe ops in closures2021-05-27T19:04:44+00:00LeSeulArtichautleseulartichaut@gmail.com2021-05-27T18:37:49+00:00urn:sha1:d1f0e9f65ce537f8026fdc207a596909c1fe4ed8Auto merge of #85110 - RalfJung:no-rustc_args_required_const, r=oli-obk2021-05-13T13:37:32+00:00borsbors@rust-lang.org2021-05-13T13:37:32+00:00urn:sha1:d2df620789cd82a6751320223cd3de87256bf15e
Remove rustc_args_required_const attribute
Now that stdarch no longer needs it (thanks `@Amanieu!),` we can kill the `rustc_args_required_const` attribute. This means that lifetime extension of references to temporaries is the only remaining job that promotion is performing. :-)
r? `@oli-obk`
Fixes https://github.com/rust-lang/rust/issues/69493
fix test suite2021-05-13T13:01:09+00:00Ralf Jungpost@ralfj.de2021-05-12T15:08:45+00:00urn:sha1:c61e8face090e2b8a0a8eca535e8b58feee25625