Hi Neels and Harald,
Is the problem related to an issue, reported by Max? https://osmocom.org/issues/2386
As I already commented, there is one possible reason:
Currently, the conv_acc_sse.c is being compiled with both -msse3 -msse4.1 CFLAGS. Some compilers (or different versions) may use the msse4.1 instruction set to optimize the whole byte code, even in the places where they are not actually used. So, one possible solution is to separate the conv_acc_sse.c to conv_acc_sse_3.c and conv_acc_sse_41.c, and then compile them with -msse3 -msse4.1 flags respectively.
If I had some basic compile / check access to the build host, I could check whether my assumption is correct.
With best regards, Vadim Yanitskiy.
On Sun, Aug 13, 2017 at 09:31:36AM +0600, Vadim Yanitskiy wrote:
Hi Neels and Harald,
Is the problem related to an issue, reported by Max? https://osmocom.org/issues/2386
Indeed looks like the same error. That issue's log shows the error with 'coding_test'; We got "Illegal instruction" upon trying to run conv_gsm0503_test. Otherwise similar.
If I had some basic compile / check access to the build host, I could check whether my assumption is correct.
It's the build host 'cumulus3' running on opensuse.org, I assume we have no / cannot get any shell access easily.
~N
On 15. Aug 2017, at 07:24, Neels Hofmeyr nhofmeyr@sysmocom.de wrote:
It's the build host 'cumulus3' running on opensuse.org, I assume we have no / cannot get any shell access easily.
cat /proc/cpuinfo cat config.log objdump -d tests/.libs/foo? to see which SSE routines were generated?
from the debian rules? If you already have an account you can fork it and compile it quickly. Build delays are quite small with OBS.
holger
-
Holger Freyther -
Neels Hofmeyr -
Vadim Yanitskiy