https://hg.paper.us.eu.org/vec/ en-us README revision history https://hg.paper.us.eu.org/vec/log/55cadb1fac4b/README
need to test it with old gcc though. :)]]> Paper <paper@tflc.us> Sun, 27 Apr 2025 02:49:53 -0400 https://hg.paper.us.eu.org/vec/log/f9ca85d2f14c/README Paper <paper@tflc.us> Sat, 26 Apr 2025 15:31:39 -0400 https://hg.paper.us.eu.org/vec/log/fd42f9b1b95e/README
I slightly edited vec.h however to use calloc directly rather
than malloc + memset.]]> Paper <paper@tflc.us> Sat, 26 Apr 2025 02:54:44 -0400 https://hg.paper.us.eu.org/vec/log/677c03c382b8/README Paper <paper@tflc.us> Fri, 25 Apr 2025 17:40:55 -0400 https://hg.paper.us.eu.org/vec/log/e26874655738/README
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.]]> Paper <paper@tflc.us> Sun, 24 Nov 2024 02:52:40 -0500 https://hg.paper.us.eu.org/vec/log/e05c257c6a23/README
ALSO!! now intrinsics are enabled at runtime, depending on what is
detected. altivec *should* still work but I only tested compiling
it.

the major version has been updated to 2.0 for this...]]> Paper <paper@tflc.us> Wed, 20 Nov 2024 04:10:37 -0500 https://hg.paper.us.eu.org/vec/log/f12b5dd4e18c/README Paper <paper@tflc.us> Tue, 22 Oct 2024 22:39:05 -0400 https://hg.paper.us.eu.org/vec/log/02a517e4c492/README Paper <paper@paper.us.eu.org> Tue, 22 Oct 2024 01:22:41 -0400