Project

General

Profile

Bug #2826

osmo-trx: different output in convolve test between x86 vs neon vs neon-vfpv4

Added by pespin 5 days ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
01/11/2018
Due date:
% Done:

0%

Spec Reference:

Description

I attach the output while running convolve_test (previously in utils/ directory) on a x86 with ssse3 and sse4.1. Now that I am implementing the infrastructure to run tests in ARM (see #2721), I found out that the output for this test is different in neon and neon-vfpv4 cases. The output is also different between the 2 neon ones. The arm testsuite.log files contains the diff aginst the x86 one (as it was the first one I used and the tool was initially wrote against it, it's the "expected" output").

I don't know if that's expected or if it's actually a bug. Assigning to Tom as he seems to be the one knowing more about this topic and who wrote the initial code for ARM.

testsuite.log-neon (2.86 KB) pespin, 01/11/2018 05:14 PM

testsuite.log-neon-vfpv4 (7.02 KB) pespin, 01/11/2018 05:15 PM

convolve_test.ok (7.6 KB) pespin, 01/11/2018 05:15 PM


Related issues

Related to OsmoTRX - Bug #2721: OsmoTRX build verification job for arm Feedback 12/07/2017
Related to OsmoTRX - Bug #2828: some osmo-trx tests failing in i586 OBS machine In Progress 01/13/2018

History

#1 Updated by pespin 5 days ago

  • Related to Bug #2721: OsmoTRX build verification job for arm added

#2 Updated by pespin about 10 hours ago

  • Related to Bug #2828: some osmo-trx tests failing in i586 OBS machine added

Also available in: Atom PDF