- 14 Jul, 2016 2 commits
-
-
Rostislav Pehlivanov authored
Adding a check for bits == 0 would still make Coverity misdetect this, so just revert to the normal way of setting the residue to 0. Signed-off-by:
Rostislav Pehlivanov <atomnuker@gmail.com>
-
Rostislav Pehlivanov authored
Can also be used in future cleanups since 99% of the time the leftover appending will just append to an already empty residue. Signed-off-by:
Rostislav Pehlivanov <atomnuker@gmail.com>
-
- 13 Jul, 2016 2 commits
-
-
Rostislav Pehlivanov authored
Signed-off-by:
Rostislav Pehlivanov <atomnuker@gmail.com>
-
Rostislav Pehlivanov authored
Shifting by more than 63 bits is undefined behavior, athough any compiler not returning 0 after shifting by any amount would be insane. Found by Coverity, fixes CID1363959 and CID1363960 Signed-off-by:
Rostislav Pehlivanov <atomnuker@gmail.com>
-
- 12 Jul, 2016 1 commit
-
-
Michael Niedermayer authored
Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 11 Jul, 2016 1 commit
-
-
Rostislav Pehlivanov authored
Still much left to optimize, but it provides a significant performance improvement - 10% for 300Mbps (1080p30), 25% for 1.5Gbps (4k 60fps) in comparison with the default implementation. Signed-off-by:
Rostislav Pehlivanov <rpehlivanov@obe.tv>
-