The parser would become confused over the purported array size of struct indexes. In reality they were always a single direct index into a struct, but it would take the object size of the represented type (EG, a vec4 would have size 4) and deference out-of-bounds memory. BUG=434033 Change-Id: I92349aa04e6faadc766cb28c04e28d5f19c4e1ec Reviewed-on: https://chromium-review.googlesource.com/230530Tested-by:Jamie Madill <jmadill@chromium.org> Reviewed-by:
Nicolas Capens <capn@chromium.org>
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| angle_implementation_unit_tests | Loading commit data... | |
| angle_tests | Loading commit data... | |
| compiler_tests | Loading commit data... | |
| deqp_tests | Loading commit data... | |
| gles_conformance_tests | Loading commit data... | |
| perf_tests | Loading commit data... | |
| preprocessor_tests | Loading commit data... | |
| standalone_tests | Loading commit data... | |
| WebGL-CTS-known-failures.txt | Loading commit data... | |
| tests.gyp | Loading commit data... |