aboutsummaryrefslogtreecommitdiffstats
path: root/src/qml/jsruntime/qv4value_p.h
diff options
context:
space:
mode:
authorFrederik Gladhorn <frederik.gladhorn@theqtcompany.com>2015-03-31 00:21:58 +0200
committerFrederik Gladhorn <frederik.gladhorn@theqtcompany.com>2015-04-13 11:03:04 +0000
commit1bff3496b172b041fcedbef0893c1d0de6c4fbc5 (patch)
tree10dfeefae7f37ec3daa87be100b8869313d1dcf1 /src/qml/jsruntime/qv4value_p.h
parentd3b0bd40ec2a2741e35e19250205af2d632a0a52 (diff)
Fix a few typos
Change-Id: Ia00949757a6f47babc1748f27e32a9644d6cc608 Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>
Diffstat (limited to 'src/qml/jsruntime/qv4value_p.h')
-rw-r--r--src/qml/jsruntime/qv4value_p.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/qml/jsruntime/qv4value_p.h b/src/qml/jsruntime/qv4value_p.h
index 2b2d275b58..cd1aef86d7 100644
--- a/src/qml/jsruntime/qv4value_p.h
+++ b/src/qml/jsruntime/qv4value_p.h
@@ -97,8 +97,8 @@ struct Q_QML_PRIVATE_EXPORT Value
/*
We use two different ways of encoding JS values. One for 32bit and one for 64bit systems.
- In both cases, we 8 bytes for a value and different variant of NaN boxing. A Double NaN (actually -qNaN)
- is indicated by a number that has the top 13 bits set. THe other values are usually set to 0 by the
+ In both cases, we use 8 bytes for a value and a different variant of NaN boxing. A Double NaN (actually -qNaN)
+ is indicated by a number that has the top 13 bits set. The other values are usually set to 0 by the
processor, and are thus free for us to store other data. We keep pointers in there for managed objects,
and encode the other types using the free space given to use by the unused bits for NaN values. This also
works for pointers on 64 bit systems, as they all currently only have 48 bits of addressable memory.
@@ -106,7 +106,7 @@ struct Q_QML_PRIVATE_EXPORT Value
On 32bit, we store doubles as doubles. All other values, have the high 32bits set to a value that
will make the number a NaN. The Masks below are used for encoding the other types.
- On 64 bit, we xor Doubles with (0xffff8000 << 32). Thas has the effect that no doubles will get encoded
+ On 64 bit, we xor Doubles with (0xffff8000 << 32). That has the effect that no doubles will get encoded
with the 13 highest bits all 0. We are now using special values for bits 14-17 to encode our values. These
can be used, as the highest valid pointer on a 64 bit system is 2^48-1.