Wenyong Huang 313ce8cb61 Fix memory/table segment checks in memory.init/table.init (#3081) ... According to the wasm core spec, the checks for the table segments in `table.init` opcode are similar to the checks for `memory.init` opcode: - The size of a passive segment is shrunk to zero after `data.drop` (or `elem.drop`) opcode is executed, and the segment can be used to do `memory.init` (or `table.init`) again - The `memory.init` only traps when `s+n > len(data.data)` or `d+n > len(mem.data)` and `table.init` only traps when `s+n > len(elem.elem)` or `d+n > len(tab.elem)` - The active segment can also be used to do `memory.init` (or `table.init`), while it behaves like a dropped passive segment https://github.com/WebAssembly/bulk-memory-operations/blob/master/proposals/bulk-memory-operations/Overview.md ``` Segments can also be shrunk to size zero by using the following new instructions: - data.drop: discard the data in an data segment - elem.drop: discard the data in an element segment An active segment is equivalent to a passive segment, but with an implicit memory.init followed by a data.drop (or table.init followed by a elem.drop) that is prepended to the module's start function. ``` ps. https://webassembly.github.io/spec/core/bikeshed/#-hrefsyntax-instr-memorymathsfmemoryinitx%E2%91%A0 https://webassembly.github.io/spec/core/bikeshed/#-hrefsyntax-instr-tablemathsftableinitxy%E2%91%A0 https://github.com/bytecodealliance/wasm-micro-runtime/issues/3020		2024-01-26 09:45:59 +08:00
..
jit_emit_compare.c
jit_emit_compare.h
jit_emit_const.c
jit_emit_const.h
jit_emit_control.c
jit_emit_control.h
jit_emit_conversion.c
jit_emit_conversion.h
jit_emit_exception.c
jit_emit_exception.h
jit_emit_function.c
jit_emit_function.h
jit_emit_memory.c
jit_emit_memory.h
jit_emit_numberic.c
jit_emit_numberic.h
jit_emit_parametric.c
jit_emit_parametric.h
jit_emit_table.c
jit_emit_table.h
jit_emit_variable.c
jit_emit_variable.h