Change getValueOrSetter to be write barrier friendly

Don't return a naked pointer into the heap, as this makes
it impossible to track where and when we're writing into it.

Change-Id: I2b9b81779ef8e9fb7a643ddda82aa6af8af459a7
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

1 files changed, 5 insertions, 0 deletions

diff --git a/src/qml/jsruntime/qv4value_p.h b/src/qml/jsruntime/qv4value_p.h
index ce7dd8fb0d..93b0dfb6d4 100644
--- a/src/qml/jsruntime/qv4value_p.h
+++ b/src/qml/jsruntime/qv4value_p.h
@@ -722,6 +722,11 @@ struct ValueArray {
     uint alloc;
     Value v[1];
 
+    void set(ExecutionEngine *e, uint index, Value newVal) {
+        Q_UNUSED(e);
+        v[index] = newVal;
+    }
+
     inline Value &operator[] (uint index) {
         Q_ASSERT(index < alloc);
         return v[index];