schmid7k

> Sorry I haven't had time to look at this yet. Been doing releases of all of the other AEAD crates, but those releases are done. > > Can you...

Both the workspace/codecov and the clippy tests are failing, because of the #![feature(portable_simd)] in my code.

Oh and btw I have implemented an optimized version of [SUNDAE](https://csrc.nist.gov/CSRC/media/Projects/lightweight-cryptography/documents/round-2/spec-doc-rnd2/SUNDAE-GIFT-spec-round2.pdf) in the meantime. It was submitted to the NIST lightweight cryptography competition as part of SUNDAE-GIFT. Would you be...

Ok codewise I am pretty much done. One thing to point out though is that `colm` as a crate name is already registered so we would have to come up...

Hey, I am currently in the process of finishing a generic, optimized implementation of [COLM](https://competitions.cr.yp.to/round2/colm.pdf), which was the second choice for use-case "defense-in-depth" of the CAESAR competition. I am in...

Hello everyone! For the past weeks I've been looking at and benchmarking native Rust implementations of cryptographic algorithms, especially AES with different block modes and after benchmarking this GCM implementation...

@tarcieri Oh yeah I think I missed that. @newpavlov Actually in my case it improves cpb by 0.1 - 0.2. I already tried all combinations of turning options on and...

I found out another interesting thing. Using nightly-2022-01-01-x86_64-unknown-linux-gnu as compiler actually improves the performance of AES-GCM on my machine compared to using the latest nightly compiler. It's a difference of...

> @Schmid7k Note that you usually do not need `-Ctarget-feature` when `-Ctarget-cpu=native` is specified. Compiler will use all available features for your CPU. > > Also, curiously enough, `-Ctarget-cpu=native` often...

I see, alright then. Btw I don't know if this is interesting to you but I found out that the performance between specifying `-Ctarget-feature` vs `-Ctarget-cpu` differs HEAVILY on the...