I have tried to build qutecom on my pandaboard ES, tracking the daily precise/armhf.
The assembler error is caused when compiling function D_UTIL_signal_up_scale, specifically the call to D_UTIL_saturate inside the loop.
A workaround to make it compile is to remove "-funroll-loops". Another one is to add "-marm", this compiles:
gcc -D_FORTIFY_SOURCE=2 -DDEBUG -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -Wmissing-prototypes -O2 -g -I/home/juan/qutecom-2.2.1+dfsg1/wifo/phapi/amrwb -fPIC -Wall -Wstrict-aliasing -Wextra -Wno-unused-parameter -fmessage-length=0 -funroll-loops -marm -o CMakeFiles/amrwb.dir/dec_util.o -c /home/juan/qutecom-2.2.1+dfsg1/wifo/phapi/amrwb/dec_util.c
This seems to be caused by a gcc bug: https://bugs.launchpad.net/bugs/926855.
Let me know if I can help with more tests.
I have tried to build qutecom on my pandaboard ES, tracking the daily precise/armhf.
The assembler error is caused when compiling function D_UTIL_ signal_ up_scale, specifically the call to D_UTIL_saturate inside the loop.
A workaround to make it compile is to remove "-funroll-loops". Another one is to add "-marm", this compiles:
gcc -D_FORTIFY_SOURCE=2 -DDEBUG -g -O2 -fstack-protector --param= ssp-buffer- size=4 -Wformat -Wformat-security -g -O2 -fstack-protector --param= ssp-buffer- size=4 -Wformat -Wformat-security -Werror= format- security -Wall -Wmissing- prototypes -O2 -g -I/home/ juan/qutecom- 2.2.1+dfsg1/ wifo/phapi/ amrwb -fPIC -Wall -Wstrict-aliasing -Wextra -Wno-unused- parameter -fmessage-length=0 -funroll-loops -marm -o CMakeFiles/ amrwb.dir/ dec_util. o -c /home/juan/ qutecom- 2.2.1+dfsg1/ wifo/phapi/ amrwb/dec_ util.c
This seems to be caused by a gcc bug: https:/ /bugs.launchpad .net/bugs/ 926855.
Let me know if I can help with more tests.