the boarder size for encoder and decoder.

Change-Id: I7291a9e06035d1533202d7a75ab40abfc1131342

Change-Id: I76c2720546b737cb63018a8ab6a3ff62a291786d

Change-Id: I7739849aa8dd5dcb0755858367fd3223587d107f

Change-Id: I2380b1b80f48496732b69c8255a485024d375f0f

Change-Id: I2dc7b3265d0a87d7a26c95b48e360c7c68cc7355

Change-Id: I46dd5ce06f36362c6274511cd1531d93926aa9bc

Reading second motion vector only when it has a second ref_frame

Change-Id: Ica72c1cd955832e15ceccda5e5a17b0bfcd83044

Change-Id: I60f2ce77638cf7d2116bc1e64b466942c76644e0

We used y_width/y_height instead of y_crop_width/y_crop_height.

Change-Id: Ia796494956f16d7a4085e043d58bdfe6de19abe7

Change-Id: I597645a15fff2d3a1104861a5c90f64394952e0b

Change-Id: I1d556ddf04ab0a98eadf412972a6977c1055446f

This fixes building with MSVC for arm.

Change-Id: Iffae0408e0c68760e87e96b9e17d9df8e8cadb1a

Change-Id: Ia63e2d05fa5dca3fb67788b0f1f28e9802ef27dd

* changes:
  test/: remove some unnecessary extern "C"s
  rtcd.sh: add extern "C" to generated headers

VS2013 Chromium builds failed with:
warning C4742: 'vp9_coefband_trans_8x8plus' has different alignment in

https://code.google.com/p/chromium/issues/detail?id=336620

Change-Id: I865f72bc23ae958531eeb5f497002c12e9a36fcd

Adds an arbitrary-size resize library for use in scaling of input
frames in a non-normative manner in the vp9 encoder. The method
used is as follows:
Downsampling - Uses a 8 tap filter for factor of 2 decimation upto
a size just higher than the desired size. Then interpolates pixels
at a precision of 1/32 pel using a set of 8-tap filters.
Upsampling - Interpolates pixels at a precision of 1/32 pel using
a set of 8-tap filters.

There is no assembly optimization yet.

Change-Id: Ib5b81e174fc139da322bb97c8214d52289d60d8a

Encoder's boarder is still 160, while decoder's boarder will be 32.
With on demand and separate boarder buffer for boarder extension.
The decoder's boarder does not need to to 160 anymore.

Change-Id: I93d5aaff15a33a2213e9761eaa37c5f2870747db