Opus 1.1.2. As experienced in previous release: """ ./test-driver: line 107: 25185 Illegal instruction "$@" > $log_file 2>&1 FAIL: celt/tests/test_unit_mathops """ -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature Url : http://lists.xiph.org/pipermail/opus/attachments/20160113/63bad4b2/attachment.pgp
We are still trying to find a reasonable solution on this one. It is not a bug in the code itself, but rather in the build system we use for tests. In the mean time, you can either safely ignore the error on the test, or build without the asm optimizations. Sorry for the inconvenience. Jean-Marc On 01/13/2016 10:31 AM, Jesus Cea wrote:> Opus 1.1.2. > > As experienced in previous release: > > """ > ./test-driver: line 107: 25185 Illegal instruction "$@" > $log_file 2>&1 > FAIL: celt/tests/test_unit_mathops > """ > > > > _______________________________________________ > opus mailing list > opus at xiph.org > http://lists.xiph.org/mailman/listinfo/opus >
On 13/01/16 17:22, Jean-Marc Valin wrote:> We are still trying to find a reasonable solution on this one. It is not > a bug in the code itself, but rather in the build system we use for > tests. In the mean time, you can either safely ignore the error on the > test, or build without the asm optimizations. Sorry for the inconvenience.Yes, after 1.1.1 release somebody (you?) told me that the failure was a test failure but the library would work OK. I have used it in production with no issues so far. Nevertheless this spurious test fail is something to address, eventually. Thanks for your hard work. Very much appreciated. -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature Url : http://lists.xiph.org/pipermail/opus/attachments/20160113/18b9158f/attachment.pgp
>>> Jesus Cea <jcea at jcea.es> schrieb am 13.01.2016 um 16:31 in Nachricht<56966DC0.9030604 at jcea.es>:> Opus 1.1.2. > > As experienced in previous release: > > """ > ./test-driver: line 107: 25185 Illegal instruction "$@" > $log_file2>&1> FAIL: celt/tests/test_unit_mathops > """The shell script most likely does not have the illegal instruction; a more useful report would be to run the thing under a debugger like gdb and then disassemble the instruction in question. Regards, Ulrich> > -- > Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ > jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ > Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ > jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ > "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ > "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ > "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
On 01/14/2016 02:23 AM, Ulrich Windl wrote:>> """ >> ./test-driver: line 107: 25185 Illegal instruction "$@" > $log_file > 2>&1 >> FAIL: celt/tests/test_unit_mathops >> """ > > The shell script most likely does not have the illegal instruction; a more > useful report would be to run the thing under a debugger like gdb and then > disassemble the instruction in question.As I said earlier, the problem is fully understood. We just don't have a solution for it yet. What happens is that the unit tests have to directly #include the C files they test because some of the functions tested are static. But some of the #included C files use intrinsics with CPU detection so they require being compiled with (e.g.) -msse4, but as soon as we include those compile flags, the compiler is free to use these instructions anywhere. And this cases the Illegal instruction failure. Jean-Marc
On 14/01/16 08:23, Ulrich Windl wrote:> The shell script most likely does not have the illegal instruction; a more > useful report would be to run the thing under a debugger like gdb and then > disassemble the instruction in question.I was under the impression of this being a well known "issue" already. If you need all details I could try to find some time to provide full details. -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature Url : http://lists.xiph.org/pipermail/opus/attachments/20160114/5564a75d/attachment.pgp