Closed GoogleCodeExporter closed 9 years ago
vp9_iht8x8_64_add_neon is using the q4-q7 registers but not saving/restoring
them.
Original comment by fgalli...@google.com
on 26 Feb 2014 at 4:48
Can a test for this be added to REGISTER_STATE_CHECK()?
Original comment by jz...@google.com
on 26 Feb 2014 at 6:05
Consider taking this patch if perf is similar
https://gerrit.chromium.org/gerrit/#/c/68922/
Original comment by johannkoenig@google.com
on 27 Feb 2014 at 3:24
ping
Original comment by jz...@google.com
on 16 Jul 2014 at 6:48
Original comment by hku...@google.com
on 17 Jul 2014 at 6:34
still failing:
fdct4x4_test.cc: DISABLED_NEON, Trans4x4HT,
fdct8x8_test.cc: DISABLED_NEON, FwdTrans8x8HT,
Original comment by johannkoenig@google.com
on 6 Nov 2014 at 1:20
Issue 898 has been merged into this issue.
Original comment by johannkoenig@google.com
on 12 Dec 2014 at 5:23
https://gerrit.chromium.org/gerrit/68922
e test exercised tx_type 0 but the code is never called that way in the encoder:
void vp9_iht8x8_add(TX_TYPE tx_type, const tran_low_t *input, uint8_t *dest,
int stride, int eob) {
if (tx_type == DCT_DCT) {
vp9_idct8x8_add(input, dest, stride, eob);
} else {
vp9_iht8x8_64_add(input, dest, stride, tx_type);
}
}
The updated patch contains all the tx_types and calls the C code if the DCT_DCT
is specified. It would probably be better to fix the test and the reference
code to indicate this is not an expected code path.
Original comment by johannkoenig@google.com
on 15 Dec 2014 at 10:55
Original issue reported on code.google.com by
jz...@google.com
on 26 Feb 2014 at 8:14