Mercurial > vec
diff README @ 23:e26874655738
*: huge refactor, new major release (hahaha)
I keep finding things that are broken...
The problem NOW was that vec would unintentionally build some
functions with extended instruction sets, which is Bad and would
mean that for all intents and purposes the CPU detection was
completely broken.
Now vec is no longer header only either. Boohoo. However this gives
a lot more flexibility to vec since we no longer want or need to
care about C++ crap.
The NEON and Altivec implementations have not been updated which
means they won't compile hence why they're commented out in the
cmake build file.
| author | Paper <paper@tflc.us> |
|---|---|
| date | Sun, 24 Nov 2024 02:52:40 -0500 |
| parents | e05c257c6a23 |
| children |
line wrap: on
line diff
--- a/README Sat Nov 23 04:09:44 2024 +0000 +++ b/README Sun Nov 24 02:52:40 2024 -0500 @@ -1,4 +1,4 @@ -vec - a tiny SIMD vector header-only library written in C99 +vec - a tiny SIMD vector library written in C99 it comes with an extremely basic API that is similar to other intrinsics libraries; each type is in the exact same format: @@ -12,6 +12,13 @@ on processors where vec has an implementation and falls back to array-based implementations where they are not. +to initialize vec, you MUST call `vec_init()' when your program starts up. + +note that `vec_init()' is NOT thread-safe, and things can and will +blow up if you call it simultaneously from different threads (i.e. you +try to only initialize it when you need to... please just initialize +it on startup so you don't have to worry about that!!!) + all of these have many operations that are prefixed with the name of the type and an underscore, for example: @@ -106,10 +113,3 @@ the result vector if the value in `vec1' is greater than or equal to the corresponding value in `vec2', else all of the bits are turned off. - -to initialize vec, you MUST call `vec_init()' when your programs starts up. - -note that `vec_init()' is NOT thread-safe, and things can and will -blow up if you call it simultaneously from different threads (i.e. you -try to only initialize it when you need to... please just initialize -it on startup so you don't have to worry about that!!!)