ref: 057c1c4034ba5b9bf360c5c1f600ebc6d0718c3a
parent: 904cb53302dfebee4a0d795ad6ccebdd5da5f542
author: James Zern <jzern@google.com>
date: Wed Mar 30 11:28:42 EDT 2016
disable vp9_diamond_search_sad_avx this results in different output than C, observed with 1080p input at speed 2. BUG=https://bugs.chromium.org/p/webm/issues/detail?id=1168 Change-Id: Ie58cf20057f4531d1b1d19c7b7eae9e642587ce5
--- a/vp9/common/vp9_rtcd_defs.pl
+++ b/vp9/common/vp9_rtcd_defs.pl
@@ -276,7 +276,7 @@
$vp9_full_search_sad_sse4_1=vp9_full_search_sadx8;
add_proto qw/int vp9_diamond_search_sad/, "const struct macroblock *x, const struct search_site_config *cfg, struct mv *ref_mv, struct mv *best_mv, int search_param, int sad_per_bit, int *num00, const struct vp9_variance_vtable *fn_ptr, const struct mv *center_mv";
-specialize qw/vp9_diamond_search_sad avx/;
+specialize qw/vp9_diamond_search_sad/;
add_proto qw/void vp9_temporal_filter_apply/, "uint8_t *frame1, unsigned int stride, uint8_t *frame2, unsigned int block_width, unsigned int block_height, int strength, int filter_weight, unsigned int *accumulator, uint16_t *count";
specialize qw/vp9_temporal_filter_apply sse2 msa/;