- 27 Feb, 2014 - 1 commit
-
-
Dmitry Kovalev authored
Change-Id: If4b5209ac14aaba6f1c1014bc0497baa8eabfaff
-
- 12 Feb, 2014 - 1 commit
-
-
Dmitry Kovalev authored
The file has implementation of only one function vpx_x86_vendor() which is unused. Change-Id: Icf8d7ee67cc8372affb7b5a436328cecdfd5e291
-
- 24 Jan, 2014 - 1 commit
-
-
James Zern authored
Change-Id: Iba9b198ce78b3f8b644feba064f83abc247e75dd
-
- 17 Dec, 2013 - 1 commit
-
-
James Zern authored
Change-Id: I4e931aadecfe1761c720b080bdd67a1875794979
-
- 09 Dec, 2013 - 1 commit
-
-
Ehsan Akhgari authored
Change-Id: Ife17fc6369ce32f36d5c7f8a2ef5a3b7724d81b9
-
- 23 Nov, 2013 - 1 commit
-
-
Yaowu Xu authored
Change-Id: I891bf936e03411ca611620e7cb2eb5081993a346
-
- 22 Nov, 2013 - 1 commit
-
-
Yaowu Xu authored
Change-Id: I0c44800db10db8d74c1ddfe89abecfd1c53d0f8d
-
- 20 Nov, 2013 - 1 commit
-
-
Erik Niemeyer authored
This CL fixes an overcite with the AVX2 support CL previously merged (Change-Id: Idc03f3fca4bf2d0afd33631ea1d3caf8fc34ec29) that prevented runtime execution of AVX2 code in WebM. Background: Starting with the Sandybridge processor, the CPUID instruction was enhanced to add various extended feature flag enumeration leaves. Reading these leaves requires an additional input value for the CPUID instruction which is stored in ECX. This change adds this second input value for all ARCH_X86 and ARCH_x86_64 targets to the CPUID macros, allowing checks of EBX bit 5 for AVX2 support. This capability will be required moving forward to check for future processor features. Change-Id: Ie9d872bc9ff68dad4b6578e4544e4dfd0ae26c36
-
- 29 Oct, 2013 - 1 commit
-
-
Erik Niemeyer authored
Change-Id: Idc03f3fca4bf2d0afd33631ea1d3caf8fc34ec29
-
- 18 Jun, 2013 - 1 commit
-
-
James Zern authored
Change-Id: I052647e13dd24354888c890f6b4a987d989552ae
-
- 02 May, 2013 - 1 commit
-
-
changjun.yang authored
Change-Id: I3fe24001cda08d7322b630f65c5e3fad881f8036
-
- 26 Apr, 2013 - 1 commit
-
-
changjun.yang authored
Change-Id: I5c49a983ced45197e1035fa5615d71b0bdad4109
-
- 05 Mar, 2013 - 1 commit
-
-
Dmitry Kovalev authored
Removing redundant 'extern' keywords, fixing formatting and #include order, code simplification. Change-Id: I0e5fdc8009010f3f885f13b5d76859b9da511758
-
- 01 Feb, 2013 - 1 commit
-
-
Frank Galligan authored
Some projects must define only win64 for Windows 64bit builds using yasm. Change-Id: I1d09590d66a7bfc8b4412e1cc8685978ac60b748
-
- 25 Jan, 2013 - 1 commit
-
-
Mark Mentovai authored
For 64-bit Mac Chromium, use private_extern for HIDDEN_DATA, the same as 32-bit Mac Chromium. Change-Id: Ica0fa9e48a47409facece691ae1e39327369083c
-
- 14 Jan, 2013 - 1 commit
-
-
John Koleszar authored
These variables have the type int64_t, not long long. long long could be a larger type than 64 bits. Emulate INT64_MAX for older versions of MSVC, and remove the unreferenced vpx_ports/vpxtypes.h Change-Id: Ideaca71838fcd3849d816d5ab17aa347c97d03b0
-
- 26 Dec, 2012 - 1 commit
-
-
John Koleszar authored
Various fixups to resolve issues when building vp9-preview under the more stringent checks placed on the experimental branch. Change-Id: I21749de83552e1e75c799003f849e6a0f1a35b07
-
- 20 Dec, 2012 - 1 commit
-
-
James Zern authored
Change-Id: If7822e6fcd0d3568b934032322b19ba3e401df26
-
- 11 Dec, 2012 - 1 commit
-
- 19 Nov, 2012 - 1 commit
-
-
Johann authored
https://codereview.chromium.org/11413061/ The Android NDK automatically manages the include directories. Trying to do so manually for the Android GYP files can cause the wrong setjmp.h to be included. Change-Id: I5c3769f983fcbad1ed602feda781690c6e4e97b3
-
- 16 Nov, 2012 - 1 commit
-
-
Johann authored
Move BUILD_LIBVPX evaluation before the include. Change-Id: I8860414c42a8161765a17bf433ff2607c0d027ca
-
- 15 Nov, 2012 - 1 commit
-
-
John Koleszar authored
Change-Id: Ib8f8a66c9fd31e508cdc9caa662192f38433aa3d
-
- 06 Nov, 2012 - 1 commit
-
-
Yaowu Xu authored
there are still a couple type of warning left, which are related to double constants assigned to float type. As those would be addressed by the conversion of transforms into integer version. This commit has left those un-dealt with. Change-Id: I48fd9b489c0c27ad6b543f4177423419f929f2bb
-
- 05 Nov, 2012 - 1 commit
-
-
John Koleszar authored
Change-Id: I25c067326153455abe1a79f8f44f70b87350e655
-
- 25 Sep, 2012 - 1 commit
-
-
Mike Frysinger authored
Add configure detection of the new x32 ABI as well as support in asm. Change-Id: Ic66a069599adeb81062090e3f11b71ee1fb97cb8
-
- 20 Aug, 2012 - 1 commit
-
-
Yaowu Xu authored
Change-Id: Iaa947e640f27e6f6eaf7d845f243536bca2df513
-
- 14 Aug, 2012 - 1 commit
-
-
Christian Duvivier authored
Change-Id: I4b911e4173da30c164bde7ea50bc80a70fbbb745
-
- 17 Jul, 2012 - 1 commit
-
-
John Koleszar authored
Approximate the Google style guide[1] so that that there's a written document to follow and tools to check compliance[2]. [1]: http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml [2]: http://google-styleguide.googlecode.com/svn/trunk/cpplint/cpplint.py Change-Id: Idf40e3d8dddcc72150f6af127b13e5dab838685f
-
- 20 Jun, 2012 - 2 commits
-
-
Johann authored
Disable unit-tests. The logging in GTest would need to be adjusted. Restructure ARM cpu detection. Flatten if-else logic. Change #if defined(HAVE_*) to #if HAVE_* because we only need to check for features that the library was actually built with. This should have been harmless, as disabled feature sets wouldn't have any features to call. Change-Id: Iea21aa42ce5f049c53ca0376d25bcd0f36f38284
-
Attila Nagy authored
Soft enable runtime cpu detect for armv7-android target, so that it can be disabled and remove dependency on 'cpufeatures' lib. Change the arm_cpu_caps implementation selection such that 'no rtcd' takes precedence over system type. Switch to use -mtune instead of -mcpu. NDK was complaining about -mcpu=cortex-a8 conflicting with -march=armv7-a, not sure why. Add a linker flag to fix some cortex-a8 bug, as suggested by NDK Dev Guide. Examples: Configure for armv7+neon: ./configure --target=armv7-android-gcc \ --sdk-path=/path/to/android/ndk \ --disable-runtime-cpu-detect \ --enable-realtime-only \ --disable-unit-tests ...armv7 w/o neon: ./configure --target=armv7-android-gcc \ --sdk-path=/path/to/android/ndk \ --disable-runtime-cpu-detect \ --enable-realtime-only \ --disable-neon \ --cpu=cortex-a9 \ --disable-unit-tests Change-Id: I37e2c0592745208979deec38f7658378d4bd6cfa
-
- 18 Jun, 2012 - 2 commits
-
-
Daniel Kang authored
Change-Id: I6802731a4d15feef5ce62993dc505ded55c40f7e
-
Ronald S. Bultje authored
Change-Id: I97aa175346683184f9430d880593b291a563e04f
-
- 12 Jun, 2012 - 1 commit
-
-
Daniel Kang authored
Updates idct/dequant mmx assembly to work with vpnext instead of vp8. Also adds x86inc.asm Change-Id: I6e147d5e89177ae449271e97e50d082eb11b078e
-
- 11 Jun, 2012 - 1 commit
-
-
John Koleszar authored
Allows building the library with the gcc -pedantic option, for improved portabilty. In particular, this commit removes usage of C99/C++ style single-line comments and dynamic struct initializers. This is a continuation of the work done in commit 97b766a4, which removed most of these warnings for decode only builds. Change-Id: Id453d9c1d9f44cc0381b10c3869fabb0184d5966
-
- 05 Jun, 2012 - 1 commit
-
-
Alpha Lam authored
This change is to allow obj_int_extract to extract all integers in the data segment. With the const keyword these variables are forced into the .rodata segment even for zero variable value. We had a problem before that zero valueed variables would get assigned to BSS segment that fooled obj_int_extract to give incorrect values. Change-Id: Icd94f80a8ab356879894ca508bf132d20b865299
-
- 30 May, 2012 - 1 commit
-
-
Alpha Lam authored
Add PRIVATE macro for adding private_extern directive for yasm to hide global symbols. This is only enabled if -DCHROMIUM is used with YASM. Also fixed a small problem with rtcd_defs.sh to guard TEMPORAL_DENOISING. Change-Id: I9027fce3ebddcf20078293e4b86b396f21da7857
-
- 24 May, 2012 - 2 commits
-
-
Alpha Lam authored
This change is to allow obj_int_extract to extract all integers in the data segment. With the const keyword these variables are forced into the .rodata segment even for zero variable value. We had a problem before that zero valueed variables would get assigned to BSS segment that fooled obj_int_extract to give incorrect values. Change-Id: Icd94f80a8ab356879894ca508bf132d20b865299
-
Alpha Lam authored
Add PRIVATE macro for adding private_extern directive for yasm to hide global symbols. This is only enabled if -DCHROMIUM is used with YASM. Also fixed a small problem with rtcd_defs.sh to guard TEMPORAL_DENOISING. Change-Id: I9027fce3ebddcf20078293e4b86b396f21da7857
-
- 02 May, 2012 - 1 commit
-
-
Timothy B. Terriberry authored
Original patch by Ginn Chen <ginn.chen@oracle.com> against libvpx v0.9.0. I've forward-ported it to the current version (which mostly involved removing hunks that were no longer relevant), since I've given up on getting Ginn to submit this upstream himself. Change-Id: I403c757c831c78d820ebcfe417e717b470a1d022
-
- 15 Mar, 2012 - 1 commit
-
-
Yaowu Xu authored
This is a code snapshot of experimental work currently ongoing for a next-generation codec. The codebase has been cut down considerably from the libvpx baseline. For example, we are currently only supporting VBR 2-pass rate control and have removed most of the code relating to coding speed, threading, error resilience, partitions and various other features. This is in part to make the codebase easier to work on and experiment with, but also because we want to have an open discussion about how the bitstream will be structured and partitioned and not have that conversation constrained by past work. Our basic working pattern has been to initially encapsulate experiments using configure options linked to #IF CONFIG_XXX statements in the code. Once experiments have matured and we are reasonably happy that they give benefit and can be merged without breaking other experiments, we remove the conditional compile statements and merge them in. Current changes include: * T...
-