aboutsummaryrefslogtreecommitdiff
path: root/test/behavior/struct.zig
diff options
context:
space:
mode:
authorDan Ellis Echavarria <19101das@gmail.com>2022-07-17 02:20:35 -0500
committerVeikka Tuominen <git@vexu.eu>2022-07-22 18:58:43 +0300
commitd1d892c83ca7beaf235147341b7e68d3619dd829 (patch)
tree8b920ee96faff0954d7c29da8144bc9fa906a36e /test/behavior/struct.zig
parent8e75ba653b03477229cf72211e8a8bfe7b071254 (diff)
downloadzig-d1d892c83ca7beaf235147341b7e68d3619dd829.tar.gz
zig-d1d892c83ca7beaf235147341b7e68d3619dd829.zip
SIMD size suggestions: suggestions code now compiles, added more
architectures The idea behind this is using the register capabilities in safe amounts, there is still some consideration to be done. + Fixed compile error using std.Target.<arch>.featureSetHas + X86 MMX and "3DNOW" 64 bits register usage considered for vector size + Added ARM Neon recommened usage of 128 bits (The size of the register) + Added AARCH64 Neon and SVE for 128 bits. SVE could use in theory up to 2048 bits, but found only evidence of functional 512 bits on a super computer, decided on using 128 bits as a safety + Added Altivec recommendation of using the 128 bits long register + Using MIPS msa 2x64bits capabilities, usage of 64 bits registers for MDMX systems, need testing on how using bigger values affect performance + Using V extension on RISC-V, which is extendable via instructions, decided on 128 bits as a value to not use all registers + in SPARC the 64 bits registers are used, a max of 32 registers are to be used for configurable simd instructions, decided on using the size of the register, need testing on performance hit on using a bigger sized register vector size
Diffstat (limited to 'test/behavior/struct.zig')
0 files changed, 0 insertions, 0 deletions