- Mar 13, 2018
-
-
Luker authoredWe ere not skipping the ESIs for the padding symbols, which is not RFC conformant Signed-off-by:Luca Fulchir <luker@fenrirproject.org>
-
Luker authored
This should make things more RFC-compatible ...but v0.1.9 will not work with v0.1.10 :( Signed-off-by:
-
- Mar 06, 2018
-
-
Luker authored
cleanup whitespace, and deactivate gitlab-runner deploy Signed-off-by: -
Luker authored
maybe I should push *all* files Signed-off-by: -
Luker authored
Signed-off-by:
-
- Nov 11, 2016
-
-
Luker authored
Signed-off-by:
-
- Nov 09, 2016
-
-
Luker authored
Signed-off-by: -
Luker authored
The RFC lies. Thanks to Mohammed Alasmar for pointing it out. Signed-off-by:
-
- Nov 02, 2016
-
-
Luker authored
Not many use this interface, uh? Signed-off-by:
-
- Oct 05, 2016
-
-
Luker authored
Signed-off-by:
-
- Sep 27, 2016
-
-
Luker authored
Squash a lot of warnings if build in 32 bit mode. also, bump up the version in the CMake :P Signed-off-by:
-
- Sep 06, 2016
-
-
Luker authored
Signed-off-by: -
Luker authored
RFC6330 lets you have 256 blocks at most. Check at the interleaver definition. The C interface did not check for correct C++ initialization. fix that, too. Signed-off-by:
-
- Jul 20, 2016
-
-
Luker authored
Luckily for us, this was never really used. Signed-off-by:
-
- Jul 15, 2016
-
-
Luker authored
Profiling was broken. We also were missing proper versioning support. Signed-off-by:
-
- Jun 02, 2016
-
-
Luker authored
Signed-off-by: -
Luker authored
Pthread fix, clang support, gcc sanitizing Signed-off-by:
-
- Mar 12, 2016
-
-
Luker authored
Sorry to ubuntu12/centos guys, but you don't even have a c++11 compiler, so you can also upgrade the cmake version. Signed-off-by:
-
- Mar 11, 2016
-
-
Luker authored
Ubuntu guys, either fix CMake or update it -.-' Signed-off-by:
-
- Mar 07, 2016
-
-
Luker authored
why stupid bugs are so hard to find? Signed-off-by: -
Luker authored
Tested on Ubuntu 14.04 Signed-off-by: -
Luker authored
Signed-off-by: -
Luker authored
Rewrote cmake, now a bit cleaner, checks for compiler flags. Added Eigen3, v3.2.8 in case it's not found on the system. Signed-off-by:
-
- Mar 03, 2016
-
-
Luker authored
test_c did not correctly calculate the memory size, although it was still fine due to the data types. the De_Interleaver was reading not-initialized data in the "skip > 0" case. Signed-off-by: -
Luker authored
Make sure the background threads actually finish before deleting the object. Signed-off-by:
-
- Dec 16, 2015
-
-
Luker authored
Make it compile everything, use cmake. Also force documentation rebuild. Signed-off-by: -
Luker authored
wrong git repository, we moved to forward iterators and we talked about encoding instead of decoding Signed-off-by: -
Luker authored
Automatically compile and push documentation on wiki, but only if there are changes Signed-off-by:
-
- Dec 14, 2015
-
-
Luker authored
Clear up the project position on licensing and contributions Signed-off-by:
-
- Nov 05, 2015
-
-
Luker authored
Signed-off-by: -
Luker authored
Signed-off-by:
-
- Nov 04, 2015
-
-
Luker authored
Signed-off-by: -
Luker authored
Multiblock alignment decoding was wrong if the block size was not aligned with the output alignment. Also, what we were calling output iterator was really a forward iterator. Get it right. Signed-off-by:
-
- Nov 03, 2015
-
-
Luker authored
I'll try to remember to check old codepaths when moving to new code :p Signed-off-by: -
Luker authored
I don't even remember why... it was just wrong... Signed-off-by: -
Luker authored
symbol might not be aligned with the output iterator, which means that we'll need to pad it. Signed-off-by: -
Luker authored
Alignment differences are harder than I thought... Signed-off-by: -
Luker authored
Signed-off-by: -
Luker authored
We were neither respecting sub-block differences, neither counting the alignment, which is not necessary the input data alignment... Signed-off-by: -
Luker authored
Bro, do you even shift? Signed-off-by:
-