about summary refs log tree commit diff
path: root/tests/codegen/simd-intrinsic
AgeCommit message (Collapse)AuthorLines
2025-07-22Rename `tests/codegen` into `tests/codegen-llvm`Guillaume Gomez-1730/+0
2025-07-20So many test updates x_xScott McMurray-473/+102
2025-07-03Block SIMD in transmute_immediate; delete `OperandValueKind`Scott McMurray-4/+2
See conversation in <https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Is.20transmuting.20a.20.60T.60.20to.20.60Tx1.60.20.28one-element.20SIMD.20vector.29.20UB.3F/near/526262799>.
2025-06-04x86 (32/64): go back to passing SIMD vectors by-ptrRalf Jung-15/+5
2025-04-20simd intrinsics with mask: accept unsigned integer masksRalf Jung-0/+57
2025-02-27remove most `simd_` intrinsic declaration in testsFolkert de Vries-193/+131
instead, we can just import the intrinsics from core
2025-02-25remove `simd_fpow` and `simd_fpowi`Folkert de Vries-174/+0
2025-02-18x86-sse2 ABI: use SSE registers for floats and SIMDRalf Jung-2/+15
2025-01-27Fix SIMD codegen tests on LLVM 20Nikita Popov-14/+14
The splat contents are printed differently on LLVM 20.
2025-01-26Consistently use the most significant bit of vector masksJörn Horstmann-13/+110
This improves the codegen for vector `select`, `gather`, `scatter` and boolean reduction intrinsics and fixes rust-lang/portable-simd#316. The current behavior of most mask operations during llvm codegen is to truncate the mask vector to <N x i1>, telling llvm to use the least significat bit. The exception is the `simd_bitmask` intrinsics, which already used the most signifiant bit. Since sse/avx instructions are defined to use the most significant bit, truncating means that llvm has to insert a left shift to move the bit into the most significant position, before the mask can actually be used. Similarly on aarch64, mask operations like blend work bit by bit, repeating the least significant bit across the whole lane involves shifting it into the sign position and then comparing against zero. By shifting before truncating to <N x i1>, we tell llvm that we only consider the most significant bit, removing the need for additional shift instructions in the assembly.
2024-11-07Update test for LLVM 20's new vector splat syntaxHans Wennborg-3/+3
that was introduced in https://github.com/llvm/llvm-project/pull/112548
2024-09-09Ban non-array SIMDScott McMurray-309/+162
2024-04-24Fix tests and blessGary Guo-1/+0
2024-02-25fix use of platform_intrinsics in testsRalf Jung-45/+45
2024-02-22[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives许杰友 Jieyou Xu (Joe)-23/+23
2024-02-20delete a test that no longer makes senseRalf Jung-47/+0
2023-12-12Fix alignment passed down to LLVM for simd_masked_loadJakub Okoński-2/+2
2023-12-09Add simd_masked_{load,store} platform-intrinsicsJakub Okoński-0/+66
This maps to the LLVM intrinsics: llvm.masked.load and llvm.masked.store
2023-07-29cg_llvm: simplify llvm.masked.gather/scatter naming with opaque pointersErik Desjardins-4/+4
With opaque pointers, there's no longer a need to generate a chain of pointer types in the intrinsic name when arguments are pointers to pointers.
2023-07-27CHECK only for opaque ptrJosh Stone-10/+10
2023-07-08Always name the return place.Camille GILLOT-89/+88
2023-04-04Allow `transmute`s to produce `OperandValue`s instead of always using `alloca`sScott McMurray-4/+47
LLVM can usually optimize these away, but especially for things like transmutes of newtypes it's silly to generate the `alloc`+`store`+`load` at all when it's actually a nop at LLVM level.
2023-02-14Try to fix codegen tests for ??? LLVM 14 ???Ben Kimock-5/+5
2023-02-14Fix codegen testsBen Kimock-92/+92
2023-02-12Enable CopyProp by default, tune the impl a bitBen Kimock-3/+0
2023-01-11Move /src/test to /testsAlbert Larsan-0/+2272