Temporarily disable AVX2 simd acceleration on linux to work around
issues with old toolchains on the integration server builds.
Linux valgrind and B2G desktop builds use an older gcc which doesn't
support the new AVX2 intrinsics. This can be resolved either by updating
the build, or splitting the target platforms into AVX and no-AVX variants.
Remove upstreamed patches, rebase stdint.patch.
Update script to work with the most recent chrome pull, upstream
hasn't been doing releases, so this is the next best way to stay
current.
It's no longer possible to build vp8 and vp9 in the same unified
source file, so most of the vp9 code is moved out of unified
sources.
There have been releases. Bump to the git commit used by the
most recent chrome pull: d95585fb0ec024f6abd96f7b02e0df58019d46af.
This patch contains changes to the update script necessary to
build the new snapshot and removes upstreamed patches.
It's no longer possible to build vp8 and vp9 in the same unified
source file, so most of the vp9 code is moved to standalone sources.
This updates our in-tree copy of libvpx to the
v1.3.0 git tag (2e88f2f2ec777259bda1714e72f1ecd2519bceb5)
libvpx 1.3.0 adds support for VP9. VP9 support is built
but not yet exposed with this commit.
Our update.sh script is replaced with update.py that can
update the build system to a given git commit.
- checkout out upstream git
- create platform dependend config files
- add/remove changed libvpx files
- update moz.build
- warn about new build categories in libvpx
