aboutsummaryrefslogtreecommitdiff
path: root/tests/benchmark
Commit message (Collapse)AuthorAgeFilesLines
* core/crypto/ecdh: Initial importYawning Angel2026-01-281-55/+34
|
* tests/benchmark: Add RNG benchmarksYawning Angel2025-11-292-0/+131
|
* -vetJeroen van Rijn2025-05-311-1/+0
|
* Vectorize `strings.prefix_length`.Jeroen van Rijn2025-05-312-0/+133
| | | | Also add `strings.common_prefix`.
* Use `time.Stopwatch` in `core:bytes` benchmarkFeoramund2025-05-291-4/+5
| | | | | | This should result in a clearer idea of how fast the procedures are running, as the loop can run without going back and forth to the system for the time.
* Add benchmarks for `runtime.memory_*` comparison proceduresFeoramund2025-05-291-0/+227
|
* Remove `Global` RegEx flag, default to unanchored patternsFeoramund2025-05-241-4/+6
|
* test/benchmarks/crypto: Improve benchmarksYawning Angel2025-03-237-552/+746
| | | | | - Use text/table for results - Add more benchmarks
* core:crypto/deoxysii: Initial importYawning Angel2025-03-231-0/+58
|
* core/crypto/aegis: Initial importYawning Angel2025-03-231-0/+58
|
* core/crypto/x448: Initial importYawning Angel2025-03-231-0/+21
|
* fix benchmarks not compiling and make sure it doesn't happen again by checkingLaytan Laats2024-10-021-4/+4
|
* Merge pull request #3962 from Feoramund/regexgingerBill2024-08-212-0/+259
|\ | | | | Add `core:text/regex`
| * Remove printing facilities for `Regular_Expression`Feoramund2024-07-241-4/+4
| | | | | | | | | | | | | | | | | | The `original_pattern` introduced a tenuous dependency to the expression value as a whole, and after some consideration, I decided that it would be better for the developer to manage their own pattern strings. In the event you need to print the text representation of a pattern, it's usually better that you manage the memory of it as well.
| * Add benchmarks for `core:text/regex`Feoramund2024-07-222-0/+259
| |
* | core/bytes: Tweak `index_byte` and `last_index_byte`Yawning Angel2024-08-191-0/+3
| | | | | | | | | | | | | | - Assume unaligned loads are cheap - Explicilty use 256-bit or 128-bit SIMD to avoid AVX512 - Limit "vectorized" scanning to 128-bits if SIMD is emulated via SWAR - Add a few more benchmark cases
* | Improve benchmarks.Jeroen van Rijn2024-08-162-45/+52
| |
* | Merge pull request #4023 from Feoramund/simd-indexJeroen van Rijn2024-08-102-0/+117
|\ \ | | | | | | Vectorize `index_byte`
| * | Merge `core:simd/util` into `core:bytes`Feoramund2024-08-102-10/+10
| | |
| * | Make `simd_util` index procs `contextless` where applicableFeoramund2024-08-091-3/+3
| | |
| * | Simplify and make `simd_util` cross-platformFeoramund2024-08-091-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | This new algorithm uses a Scalar->Vector->Scalar iteration loop which requires no masking off of any incomplete data chunks. Also, the width was reduced to 32 bytes instead of 64, as I found this to be about as fast as the previous 64-byte x86 version.
| * | Add benchmarks for vectorized `index_*` procsFeoramund2024-08-062-0/+118
| |/
* | core/crypto/chacha20: Change API terminology to be consistent with AESYawning Angel2024-08-101-8/+8
| |
* | core/crypto/chacha20poly1305: Change the interface to match GCMYawning Angel2024-08-101-1/+4
|/
* tests/benchmark/crypto: Benchmark AES256-CTRYawning Angel2024-07-161-0/+56
|
* utilize `odin test -all-packages` instead of (make/bat) scripts for running ↵Laytan Laats2024-06-073-27/+4
| | | | tests
* Disable `FANCY_OUTPUT` in Odin test scriptsFeoramund2024-06-022-3/+3
| | | | This should tidy up the CI output logs a bit.
* Add missing benchmarks build.bat.Jeroen van Rijn2024-06-021-0/+13
|
* Factor benchmarks out into tests\benchmark\<pkg>Jeroen van Rijn2024-06-023-0/+588