qt/qtdeclarative.git, branch v5.8.0

Fix incorrect JavaScript evaluation with the JIT

2017-01-06T10:09:42+00:00

This is a regression from commit
7e14b531b294650733a61a9365eb9ef74f8a7a90, that replaced a QHash with a vector of intervals. When an interval is split, it
may happen that during one interval a temp is stored in a register and
in the second interval it ends up in a different register or the stack.
The _liveIntervals variable, formerly the _intervalForTemp hash, tracked
the intervals per temp when going through the basic blocks and
statements during the renumbering phase. Indexing uniquely by temp is
important therefore for _liveIntervals and addNewIntervals violated that
by replacing the QHash replacement

    _intervalForTemp[i->temp()] = i;

with

    _liveIntervals.push_back(i);

This is how we may end up with multiple intervals for the same temp (in
different locations), and when doing the linear lookup we'd only find
the first. Restoring the replacement behavior and thus ensuring
uniqueness by temp fixes the miscompilations.

Task-number: QTBUG-57779
Change-Id: Ib8f53672b66750f68e16e47794dbc5f39989e1a2
Reviewed-by: Lars Knoll 
Reviewed-by: Robin Burchell

Add changes file for 5.8.0

2016-12-09T12:14:10+00:00

Change-Id: I29311143b04cdd4d6a13980ccb57b7867bcf9c53
Reviewed-by: Robin Burchell

change type of QQuickPointerDevice::uniqueId to QPointingDeviceUniqueId

2016-12-09T07:37:57+00:00

This will make it easier to change or extend further, in case some
future device has some sort of unique serial number which does not
fit in a quint64.

Task-number: QTBUG-54616
Change-Id: I8f20b13d75b937fce6a66653476d0d25f2abf34b
Reviewed-by: Jan Arve Sæther

rename QPointerUniqueId -> QPointingDeviceUniqueId

2016-12-09T07:37:49+00:00

Several people agreed that the name was confusing and that this one
is better.

Task-number: QTBUG-54616
Change-Id: Ie9d24fc6e233949be36c8b6ee2650080a8a3506e
Reviewed-by: Sune Vuorela 
Reviewed-by: Jan Arve Sæther

Calqlatr Example: Pass the third arg to the mapToItem() calls

2016-12-09T06:22:45+00:00

Apparently the mapToItem version used in the example requires at
least three arguments, for some reason only two were provided,
the item and the mouseX coordinate. Without the third argument,
mouseY coordinate, the drag operation to move the display fails
with warnings on the console.

Task-number: QTBUG-57514
Change-Id: If1b16c27539bd90a2d20203dedc26f11ac2a0942
Reviewed-by: Shawn Rutledge 
Reviewed-by: Topi Reiniö 
Reviewed-by: Mitch Curtis

V4 Interpreter: reset the exception handler for every catch block

2016-12-08T05:34:38+00:00

If an exception handler consists of multiple basic-blocks, and is then
followed by a finally block (for example: a catch block with a throw
followed by a return, and then a subsequent finally block), then the
finally block can be reached before the exception handler is reset by
skipping the second block of the catch handler with a throw. As the
finally block will then rethrow, and the old exception handler is still
there, it will end in an endless loop.

The fix is to reset the exception handler for every catch block. The
problem occurred in ch12/12.14/S12.14_A13_T3

Change-Id: I968b62c6c2af30af32e2717a9ce85f852523dbe8
Reviewed-by: Simon Hausmann

Don't read members of the binding after it has been freed

2016-12-06T11:48:55+00:00

Fixes a use after free valgrind error (and thus a potential
crash) in tst_qqmljavascript::selfDeletingBinding that got
introduced with change e7f28bd13b18cfcb36ef41804029b9b296117002

Change-Id: Ia6b69af199c0f2af1cc0d33d4f13a8593b2c6d51
Reviewed-by: Simon Hausmann

comment out all uses of QPointerUniqueId temporarily

2016-12-04T07:45:24+00:00

The next step is to rename it, but we do this first to avoid breaking
CI while it's renamed in qtbase.

Task-number: QTBUG-54616
Change-Id: Iae3a098b9ab5571599af838d19b1869b84b2165f
Reviewed-by: Jan Arve Sæther

Fix compilation error with ICC 17: it doesn't like auto and comma

2016-12-04T07:40:48+00:00

The error is a warning upgraded via -Werror and the message doesn't even
make sense to me:

error #3373: nonstandard use of "auto" to both deduce the type from an
initializer and to announce a trailing return type

Intel-Issue-ID: 6000164202
Change-Id: I73fa1e59a4844c43a109fffd148caf09a1952e92
Reviewed-by: Simon Hausmann

Fix build of QtQuick compiler generated code with popScope()

2016-12-02T07:28:27+00:00

After commit 5e6bf607ee1e466eebabb7b8114c9f5e8fc40a9e we would not have
an exception check template matching anymore that sets NeedsCheck to
false, and consequently generated code that would try to call popScope()
with an ExecutionEngine instead of a NoThrowEngine.

Task-number: QTRD-2219
Change-Id: Iddf8218d1efb9af77c9a5f7ef84b9998fb167ef5
Reviewed-by: Erik Verbruggen