Re: Profiling data of decoding EPDAN compressed bitmap

After looking at the code, I don't think reusing table implementation would be easy - the approaches are too different as well as underlying data structures.

On 07/13/2016 11:53 AM, Holger Freyther wrote:

osmo_t4_decode (got the runlen step and such inlined). What I think decompress_crbb is doing better is 1st not using bitvec as input but iterating over the bits itself and being more direct in applying the codeword in the result. What I am missing and have to check is if search_runlen can be implemented around the "table" we have and what the performance difference is. I have asked Max for help.