On 2021-02-01 4:47 p.m., John David Anglin wrote: > Test tst_qjsvalueiterator fails as follows: > dave@mx3210:~/debian/qtdeclarative-opensource-src$ > /home/dave/debian/qtdeclarative-opensource-src/qtdeclarative-opensource-src-5.15.2+dfsg/tests/auto/qml/qjsvalueiterator/tst_qjsvalueiterator > ********* Start testing of tst_QJSValueIterator ********* > Config: Using QtTest library 5.15.2, Qt 5.15.2 (unknown-big_endian-ilp32 > shared (dynamic) release build; by GCC 10.2.1 20210110), debian unknown > PASS : tst_QJSValueIterator::initTestCase() > PASS : tst_QJSValueIterator::iterateForward(no properties) > PASS : tst_QJSValueIterator::iterateForward(foo=bar) > PASS : tst_QJSValueIterator::iterateForward(foo=bar, baz=123) > PASS : tst_QJSValueIterator::iterateForward(foo=bar, baz=123, rab=oof) > PASS : tst_QJSValueIterator::iterateArray(no elements) > PASS : tst_QJSValueIterator::iterateArray(0=foo, 1=barr) > PASS : tst_QJSValueIterator::iterateArray(0=foo, 3=barr) > > === Received signal at function time: 70ms, total time: 310ms, dumping stack > === In looking at the JS Value encoding in src/qml/common/qv4staticvalue_p.h, I suspect there might be an issue with NaN/Inf values on hppa. hppa and early mips used a different representation for signalling and quiet NaNs. This would need to be taken into account in converting between JS and hardware values.
It seems hppa is the only big endian ilp32 architecture. Dave -- John David Anglin dave.ang...@bell.net
