summaryrefslogtreecommitdiff
path: root/test/example/c-api-multiple-tables.txt
Commit message (Collapse)AuthorAgeFilesLines
* Fix element segment ordering in Print (#3818)Abbas Mashayekh2021-04-201-1/+1
| | | | | | | | | | | We used to print active element segments right after corresponding tables, and passive segments came after those. We didn't print internal segment names, and empty segments weren't being printed at all. This meant that there was no way for instructions to refer to those table segments after round tripping. This will fix those issues by printing segments in the order they were defined, including segment names when necessary and not omitting empty segments anymore.
* [reference-types] Support passive elem segments (#3572)Abbas Mashayekh2021-03-051-2/+3
| | | | | | | | | | | Passive element segments do not belong to any table, so the link between Table and elem needs to be weaker; i.e. an elem may have a table in case of active segments, or simply be a collection of function references in case of passive/declarative segments. This PR takes Table::Segment out and turns it into a first class module element just like tables and functions. It also implements early support for parsing, printing, encoding and decoding passive/declarative elem segments.
* Slightly improve table C API (#3604)Daniel Wirtz2021-02-261-2/+2
| | | Uses BinaryenIndex instead of int to mirror parameter types in table construction, and adds setters for name, initial and max.
* [reference-types] remove single table restriction in IR (#3517)Abbas Mashayekh2021-02-091-0/+20
Adds support for modules with multiple tables. Adds a field for the table name to `CallIndirect` and updates the C/JS APIs accordingly.