diff options
author | Alon Zakai <azakai@google.com> | 2022-10-19 11:02:33 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-10-19 11:02:33 -0700 |
commit | 18273489e9433e399cc4f088e9352c08aec13369 (patch) | |
tree | a3f8274aee790918dfb26326dcc5ec2e33c1d5ec /src/wasm/wat-parser.cpp | |
parent | 3b1df7e5c329d9600cfadd513b557af618c007aa (diff) | |
download | binaryen-18273489e9433e399cc4f088e9352c08aec13369.tar.gz binaryen-18273489e9433e399cc4f088e9352c08aec13369.tar.bz2 binaryen-18273489e9433e399cc4f088e9352c08aec13369.zip |
[Wasm GC] Use Cones in GUFA data reads and writes (#5157)
When we read from a struct/array using a cone type, read from the types in the cone
and nothing else. Previously we used the declared type in the wasm, which might be
larger (both in the base type and the depth). Likewise, in a write.
To do this, this extends ConeReadLocation with a depth (previously the depth there
was assumed to be infinite, and now it is to a potentially limited depth).
After this we are fully utilizing cone types in GUFA, as the test changes show (or at
least I can't think of any other uses of cones).
Diffstat (limited to 'src/wasm/wat-parser.cpp')
0 files changed, 0 insertions, 0 deletions