Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2021-02-10 Thread Dmitry Shachnev
On February 9, 2021 11:48:08 PM GMT+03:00, John David Anglin wrote: > Is there a public qtdeclarative repository that can be cloned with > git? Yes: https://code.qt.io/qt/qtdeclarative.git -- Dmitry Shachnev

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2021-02-09 Thread John David Anglin
On 2021-02-09 2:02 p.m., Dmitry Shachnev wrote: > That's because the relevant code is no longer present in 5.12, see: > > https://codereview.qt-project.org/c/qt/qtdeclarative/+/254748 Is there a public qtdeclarative repository that can be cloned with git? -- John David Anglin

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2021-02-09 Thread Dmitry Shachnev
Hi again! On Sat, Feb 06, 2021 at 12:28:42PM -0500, John David Anglin wrote: > There was a crashing bug patch in 5.11.3-4 that was removed in 5.12.2-1. > Code was changed. That's because the relevant code is no longer present in 5.12, see:

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2021-02-06 Thread John David Anglin
On 2021-02-05 7:41 a.m., Dmitry Shachnev wrote: > For NaN, you probably need to check if these masks are correct: > > https://sources.debian.org/src/qtdeclarative-opensource-src/5.15.2+dfsg-4/src/qml/common/qv4staticvalue_p.h/#L285 >

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2021-02-05 Thread Dmitry Shachnev
On Thu, Feb 04, 2021 at 01:39:04PM -0500, John David Anglin wrote: > That's the dichotomy.  I know hppa but not Qt.  It painful to find the > parts of Qt that depend on endianness, stack layout, and possibly the NaN > representation. I also don’t know the QML / V4 engine code well. But the

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2021-02-04 Thread John David Anglin
On 2021-02-04 1:25 p.m., Dmitry Shachnev wrote: > I know almost nothing about hppa, and I don’t have much time to debug this, > but if you provide a patch that will make more tests pass on hppa (and does > not break other architectures), I will be happy to apply it (and help with > pushing it

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2021-02-04 Thread Dmitry Shachnev
Hi John! On Tue, Feb 02, 2021 at 10:07:52AM -0500, John David Anglin wrote: > 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

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2021-02-02 Thread John David Anglin
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 >

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2021-02-01 Thread John David Anglin
On 2020-11-09 1:35 p.m., Dmitry Shachnev wrote: > I only found one old bug report and it was fixed: > https://bugreports.qt.io/browse/QTBUG-44268 I think we have to go back to the original backtrace and the test failures. I thought that for a bit that we might have a problem similar to ia64 and

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2020-11-09 Thread Dmitry Shachnev
On Sat, Nov 07, 2020 at 06:07:02PM -0500, John David Anglin wrote: > That's what I was afraid of.  If these assumptions are localized, it would > help if you could point them out. I can't point them out :( But I can suggest you to contact upstream (via the mailing list or via bugreports.qt.io)

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2020-11-07 Thread John David Anglin
Hi Dmitry, On 2020-11-07 1:20 p.m., Dmitry Shachnev wrote: > I think the problem is not that hppa is not detected, but rather that the code > has some assumptions about the stack growing down. The QML engine has a lot of > low-level code... That's what I was afraid of.  If these assumptions are

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2020-11-07 Thread Dmitry Shachnev
Hi John! On Thu, Nov 05, 2020 at 03:49:47PM -0500, John David Anglin wrote: > The attached patch fixes > qtdeclarative-opensource-src-5.15.1+dfsg.orig/src/3rdparty/masm/wtf/Platform.h > for hppa.  That's the only platform configuration that I could find in the > package. I think the problem is

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2020-11-05 Thread John David Anglin
On 2020-11-05 12:20 p.m., Dmitry Shachnev wrote: >> Another possibility is doStoreOnStack doesn't work on hppa. > I think the complete QML engine may be broken on hppa, not just qmlcachegen. > > A lot of tests are failing — search for FAIL! in the build log: > >

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2020-11-05 Thread Dmitry Shachnev
Hi! On Thu, Nov 05, 2020 at 11:25:37AM -0500, John David Anglin wrote: > The segfault is caused by stack overflow.  On hppa, the kernel config > parameter CONFIG_MAX_STACK_SIZE_MB sets the maximum stack size.  This is > because the main stack is allocated at the top of memory and the stack grows

Bug#973659: qtdeclarative5-dev-tools: qmlcachegen segfaults on hppa

2020-11-02 Thread John David Anglin
Package: qtdeclarative5-dev-tools Version: 5.14.2+dfsg-3 Severity: normal Dear Maintainer, The qtgraphicaleffects-opensource-src package fails to build on hppa because qmlcachegen faults with out-of bounds references: do_page_fault() command='qmlcachegen' type=15 address=0xf98c4020 in