On 27/07/14 11:10, Christophe Gisquet wrote:
> 2014-07-27 10:43 GMT+02:00 Christophe Gisquet :
>> On the other hand, this is with little to no SIMD, so it might be
>> bigger with enough dsp code.
>
> Actually, it's just put_unweighted_pred that is now running using
> known square sizes, so you've
2014-07-27 10:43 GMT+02:00 Christophe Gisquet :
> On the other hand, this is with little to no SIMD, so it might be
> bigger with enough dsp code.
Actually, it's just put_unweighted_pred that is now running using
known square sizes, so you've allowed the compiler to unroll these
specific functions
Hi,
2014-07-14 12:55 GMT+02:00 Luca Barbato :
> Square prediction units are the most common.
> About 0.7% faster on 4k videos.
How big is the code size increase? What system were you using?
Where from are the sequences used? I'm asking this because I wonder
how much this figure depends on video
On 23/07/14 21:43, Anton Khirnov wrote:
>
> On Mon, 14 Jul 2014 12:55:36 +0200, Luca Barbato wrote:
>> Square prediction units are the most common.
>> About 0.7% faster on 4k videos.
>> ---
>> libavcodec/hevc.c | 64
>> +--
>> libavcodec/hevcd
On Mon, 14 Jul 2014 12:55:36 +0200, Luca Barbato wrote:
> Square prediction units are the most common.
> About 0.7% faster on 4k videos.
> ---
> libavcodec/hevc.c | 64
> +--
> libavcodec/hevcdsp.c | 6
> libavcodec/hevcdsp.h
Square prediction units are the most common.
About 0.7% faster on 4k videos.
---
libavcodec/hevc.c | 64 +--
libavcodec/hevcdsp.c | 6
libavcodec/hevcdsp.h | 2 ++
libavcodec/hevcdsp_template.c | 16 +++
4 files c
