1. 21 Mar, 2014 21 commits
  2. 20 Mar, 2014 13 commits
  3. 19 Mar, 2014 6 commits
    • Dmitry Kovalev's avatar
      33469800
    • Jingning Han's avatar
      Enable variable block size test in non-RD mode decision · 60f9ebc3
      Jingning Han authored
      This is an initial attempt to allow variable block size partition
      in non-RD coding flow. It tests 8x8, 16x16 and 32x32 block size per
      64x64 block, all using non-RD mode decision and the associated rate
      distortion costs from modeling, then selects the best block size to
      encode the entire 64x64 block. Such operations are triggered every
      other 3 frames. The blocks of intermediate frames will reuse the
      collocated block's partition type.
      
      It improves the compression performance by 13.2%. Note that the gains
      are not evenly distributed. For many hard clips, the compression
      performance is improved by 20% to 28%. Local speed test shows that
      it will also increase runtime by 50%, as compared to speed -7. It is
      now enabled in speed -6 setting.
      
      Change-Id: Ib4fb8659d21621c9075b3c369ddaa9ecb0a4b204
      60f9ebc3
    • Dmitry Kovalev's avatar
      Moving common code into vp9_update_mv_count(). · c9ec26f1
      Dmitry Kovalev authored
      Change-Id: I512482853bdf2695fbdf1c705a2ada354ccf76cf
      c9ec26f1
    • Dmitry Kovalev's avatar
      Adding alloc_mi() function. · 4b37dc8d
      Dmitry Kovalev authored
      Change-Id: I3b944884c048f589c86e0169aeb3c3855bc8b729
      4b37dc8d
    • Martin Storsjo's avatar
      ads2armasm_ms: Add an ALIGN 4 after ENDP · 5182befa
      Martin Storsjo authored
      This makes sure that labels for data symbols directly after
      functions get properly 4-byte-aligned (when the source is assembled
      in thumb mode).
      
      Previously, if declaring a data symbol directly after a function, the
      symbol could end up pointing to the unaligned address (if the total
      size of the thumb function didn't end up being a multiple of 4). The
      data in the symbol itself ended up aligned, but the symbol pointed to
      the preceding unaligned position.
      
      That is, a source file looking like this:
      ---
         ...
         ENDP
      
      symbol
         DCD 0x12345678
      ---
      
      could end up being assembled into
      symbol:
        xxxxx2: 0000
        xxxxx4: 5678
        xxxxx6: 1234
      
      (This doesn't happen if the symbol label is on the same line as the
      DCD directive.)
      
      By adding an ALIGN 4 directly after the ENDP we make sure the symbol
      itself gets aligned properly.
      
      This isn't an issue with the original, untranslated arm source,
      since it only is built in arm mode where all instructions are 4 byte,
      and since the gnu assembler automatically adds the padding before the
      symbol even in thumb mode.
      
      Change-Id: Iadbeebd656b0197e423e79a12a7d3ef8859cf445
      5182befa
    • Yaowu Xu's avatar
      Remove duplicate declaration · 7ef16efc
      Yaowu Xu authored
      Change-Id: Ic8e52a89e0df816c38cd8ff1b7c53862b9a6dff2
      7ef16efc