1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
# Contributing to SIMDe
First off, if you're even reading this, thank you! There is a lot of
work to do, and any help is appreciated.
If you haven't already, please read the
[README](https://github.com/simd-everywhere/simde/blob/master/README.md). The
[wiki](https://github.com/simd-everywhere/simde/wiki) also has some good
information, especially the
[FAQ](https://github.com/simd-everywhere/simde/wiki/FAQ) and a guide on how to
[implement a new
function](https://github.com/simd-everywhere/simde/wiki/Implementing-a-New-Function).
For information on developing for architectures you don't have access
to, please see the [Development
Environment](https://github.com/simd-everywhere/simde/wiki/Development-Environment)
page on the wiki.
If you still have questions, or if anything below doesn't make sense
to you, please feel free to use the [issue
tracker](https://github.com/simd-everywhere/simde/issues) or the [mailing
list](https://groups.google.com/forum/#!forum/simde) to ask. I know
the SIMDe documentation needs a lot of improvement, and asking
questions will help us understand what is missing, so please don't be
shy!
## Building the Tests
SIMDe contains an extensive test suite used for development. Most
users will never need to build the suite, but if you're contributing
code to SIMDe you'll need to build them.
Here is the basic procedure for compiling and running the tests:
### On Unix
```bash
mkdir -p build
cd build
CFLAGS="-march=native" CXXFLAGS="-march=native" meson setup ..
ninja test
```
Note that `-march=native` may not be the right flag for your compiler.
That should work for most compilers on x86/x86_64, though MSVC is an
exception (try `/arch:AVX2` instead of `-march=native`). On other
architectures please consult your compiler documentation to find out
what flags you should use to enable the SIMD extension for your target
platform. Here are a few to try:
* ARM:
* `-march=armv8-a+simd` (for AArch64)
* `-march=armv8-a+simd -mfpu=auto` (for ARMv8)
* `-march=armv7-a -mfpu=neon` (for ARMv7)
* POWER
* `-mcpu=native`
If you need a flag not listed above, please let us know so we can add
it to the list.
#### Single test
Compile and run a specific test. Switch `emul` for `native`, and `/c` for `/cpp`
as needed.
```
meson test --print-errorlogs arm/neon/qabs/emul/c
```
Using `meson test` instead of `ninja` and directly executing the test
is helpful for emscripten and other architectures where are there extra steps needed
(changing the directory, using `v8` to run`, etc..).
Just compile one specific test with verbose output. Useful for debugging
compiler errors.
```
meson compile --verbose test/arm/neon/qabs-emul-c
```
### On Windows:
```bash
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvars64.bat" arm64
mkdir build
cd build
set CFLAGS="/std:c11"
set CXXFLAGS="/Zc:preprocessor"
meson setup ..
ninja test
```
Note change arm64 to x64 on x86_64 CPU.
You may also want to take a look at the
[Docker container](https://github.com/simd-everywhere/simde/tree/master/docker)
which has many builds pre-configured, including cross-compilers and emulators.
## Coding Style
SIMDe has an [EditorConfig](https://editorconfig.org/) file to
configure your editor for things like tabs vs. spaces, how many spaces,
etc. If you use an editor which doesn't support it out of the box then
odds are good there is a plugin you can download; please do so.
For other coding style information, please see the
[Coding Style](https://github.com/simd-everywhere/simde/wiki/Coding-Style)
document in the Wiki.
|
