From 4dd053eb5795e53470bac015a24756f3454b8a85 Mon Sep 17 00:00:00 2001 From: hkuang Date: Fri, 7 Mar 2014 11:21:28 -0800 Subject: [PATCH] Disable sixtap_predict_test for neon. Neon code unit test is failing now due to save/restore neon register operations are not done inside this function, but outside of it. Disable it now until VP8 neon code get cleaned up. Bug: 725 Change-Id: Id1ff1ef50a0e894b41c820a310ff8ba31ef12d18 --- test/sixtap_predict_test.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/sixtap_predict_test.cc b/test/sixtap_predict_test.cc index 1b2f03f53..0c600f402 100644 --- a/test/sixtap_predict_test.cc +++ b/test/sixtap_predict_test.cc @@ -198,7 +198,7 @@ const sixtap_predict_fn_t sixtap_16x16_neon = vp8_sixtap_predict16x16_neon; const sixtap_predict_fn_t sixtap_8x8_neon = vp8_sixtap_predict8x8_neon; const sixtap_predict_fn_t sixtap_8x4_neon = vp8_sixtap_predict8x4_neon; INSTANTIATE_TEST_CASE_P( - NEON, SixtapPredictTest, ::testing::Values( + DISABLED_NEON, SixtapPredictTest, ::testing::Values( make_tuple(16, 16, sixtap_16x16_neon), make_tuple(8, 8, sixtap_8x8_neon), make_tuple(8, 4, sixtap_8x4_neon)));