a111dd26b1
Make clear why we don't need to assert against out-of-bounda accesses in the generated code, provided the code point is within its bound, (Using one table's early entries as indices into later in the same table at which to look up indices into another table made it a little hard to work out what was going on, especially as nothing told me about the early / late distinction. Record what I discovered, to save the next person to stumble into this some confusion.) Change-Id: I8e5771a7f3d70c1911aeae1b0cabe5c47bc7e9c7 Reviewed-by: Konstantin Ritt <ritt.ks@gmail.com> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> |
||
---|---|---|
.. | ||
accessibilityinspector | ||
aglfn | ||
cmake | ||
corelib/qurl-generateTLDs | ||
edid | ||
glgen | ||
gradientgen | ||
harfbuzz | ||
includemocs | ||
integrity | ||
lexgen | ||
locale_database | ||
plugintest | ||
qfloat16-tables | ||
unicode | ||
x86simdgen | ||
xkbdatagen |