- Mar 06, 2018
-
-
Luker authoredThe OTI fields and the symbol id are all in big endian. We used the host endianness instead. fix that. Ticket #22 Signed-off-by:
Luca Fulchir <luker@fenrirproject.org>
-
- Mar 03, 2018
-
-
Luker authored
...which brings some API breakage :( notable things: * C and C++ names for structs and variables are now in sync * common.hpp is much easier to read * added "trcked by" "tracks ..." to know that some things are to be kept in synch between C and C++ * "RaptorQ_Dec_Result" name was too similar to "RaptorQ_Decoder_Result". The C++ version calls it "Decoder_wait_res", let's go with that, at least it is more different and actually more to the point. Signed-off-by: -
Luker authored
Just using wait() on the future does not give the same semantic meaning as decode_once, which can sometimes be needed. Also, the C++ API exposes that, so the C API should really track it. Signed-off-by: -
Luker authored
From is a void** not a void* Copy-paste is as bad as ever, I guess... Signed-off-by: -
Luker authored
I forgot to delete and set the ptr to nullptr for the RaptorQ_ptr Signed-off-by:
-
- Feb 27, 2018
-
-
Luker authored
Ticket #8 Finally move the documentation to track the RFC6330 namespace for both C and C++ APIs fixes are related to the documentation * decode_symbol was forgotten * future_state uniformed between RAW and RFC * renamed a couple of RaptorQ__v1 in RFC6330__v1 Signed-off-by:
-
- Feb 05, 2018
-
-
Luker authored
symbol++ did not work. also: we don't use the default second parameter anymore Signed-off-by:
-
- Jan 08, 2018
-
-
Luker authored
Renamed Decoder_aligned_res in Decoder_written It's really the same, just that the RFC forces the sizes of the memebers, while in the RAW API we can keep size_t also: bump up to 1.0.0-alpha1, things are much better and consistent now Signed-off-by: -
Luker authored
The rfc API still used that "void* &" switch to void** which makes more sense for the C interface. Also, that's what we use on the RAW api While we are at it, force the template to specify both input *and* output typenames, so that it is easier to switch between the linked library and the header-only inline the template so that it can be reincluded multiple times without redeinitions Signed-off-by: -
Luker authored
The flags "complete" and "no_pool" are actually perfectly compatible. Signed-off-by: -
Luker authored
Signed-off-by:
-
- Jan 07, 2018
-
-
Luker authored
Using a struct makes it more portable for C, and we avoid some first/second which nobody ever understand/remeber the meaning Signed-off-by: -
Luker authored
Signed-off-by:
-
- Jan 04, 2018
-
-
Luker authored
Signed-off-by:
-
- Dec 21, 2017
-
-
Luker authored
add ability for the decoder to clear the data, so that the memory can be reused again. Signed-off-by:
-
- Dec 19, 2017
-
-
Luker authored
Fix unusable apis, port a couple of windows fixes Signed-off-by:
-
- Dec 12, 2017
-
-
Luker authored
Signed-off-by: -
Luker authored
Signed-off-by:
-
- Dec 11, 2017
-
-
Luker authored
* Wrong declaration of C functions * fix including of split caches for header-only and linked library CmakeList: split the sources for linked and header-only Signed-off-by: -
Luker authored
See github #12. Signed-off-by: -
Luker authored
Signed-off-by: -
Luker authored
Multi-process computation sharing is a pain, and also a security hazard. Ignore it, let's fix everything else first Signed-off-by:
-
- Jan 02, 2017
-
-
Luker authored
set default/delete for all class constructors Signed-off-by:
-
- Dec 30, 2016
-
-
Luker authored
Signed-off-by: -
Luker authored
Signed-off-by:
-
- Dec 27, 2016
-
-
Luker authored
Signed-off-by:
-
- Dec 15, 2016
-
-
Luker authored
RFC says one thing, but we did an other, which was still completely equivalent. Signed-off-by: -
Luker authored
Maybe. we'll see. Signed-off-by:
-
- Nov 25, 2016
-
-
Luker authored
typo. make things compile again Signed-off-by: -
Luker authored
No changes here. Just formatting. Signed-off-by:
-
- Nov 10, 2016
-
-
Luker authored
Benchmarks now make more sense. New RAW API is about 30% faster than the RFC. Precomputations only make sense after a certain size, probably dependent on symbol size ? Signed-off-by:
-
- Nov 09, 2016
-
-
Luker authored
Unexpected timings again. Will investigate. Signed-off-by: -
Luker authored
Kind of untested, but *should* withstand overflow of counters now. Signed-off-by:
-
- Nov 08, 2016
-
-
Luker authored
RFC6330 lies. No big deal, just a change of names. Many thanks to Mohammed Alasmar Signed-off-by:
-
- Nov 05, 2016
-
-
Luker authored
Signed-off-by:
-
- Nov 02, 2016
-
-
Luker authored
Too many iterators, all the same. a couple of macros are better than that much duplication Signed-off-by: -
Luker authored
Also, a longstanding, never-triggered bug got fixed. More work need to be done for decoder iterators, and the <future>, which is not supported in C++98 Signed-off-by:
-
- Oct 31, 2016
-
-
Luker authored
Signed-off-by: -
Luker authored
Smallfixes, really Signed-off-by: -
Luker authored
Signed-off-by:
-