binaryen.ml
binaryen.ml copied to clipboard
grain-lang
OCaml bindings for Binaryen.
Closes #189 . One note about this API: the Binaryen constructor for `try` accepts either a list of catch expressions or a delegate tag. Keeping in line with the other...
Binaryen has some optimization options, such as `closedWorld`, which affect some optimization passes. We should add an API to set these options.
Binaryen 111 added C APIs for most GC-related functions, such as: https://github.com/WebAssembly/binaryen/compare/version_110...version_111#diff-5d2db7a99567fbac5e617fd39709fbdca0a2d22b92a97d5c3515caf7dba9f78bR1035-R1154 and https://github.com/WebAssembly/binaryen/compare/version_110...version_111#diff-5d2db7a99567fbac5e617fd39709fbdca0a2d22b92a97d5c3515caf7dba9f78bR2335-R2706 However, they left them all as TODO in the JS code (see https://github.com/WebAssembly/binaryen/compare/version_110...version_111#diff-9f4ceff4b9bcc272e133f83651e487c15f772e6115c88023c2435cc5226d8b68R2438-R2448) We generally don't...
While working on Binaryen 113 bindings, I noticed that they renamed `BinaryenArrayInit` and related operations to `BinaryenArrayNewFixed`. We didn't have bindings for the original names, so I didn't add the...
I'm looking at our Expression module and I notice that a lot of naming is to guide the usage of the APIs. Can we use our type system to guard...
As I was updating the bindings for 112, I noticed that we don't have these APIs.
I think that if we convert the stubs to `.cpp` files, we won't need the `-cc` flag.
Closes #174 Blocked by the Binaryen.js API for atomics being non-uniform with the C API
WIP branch at https://github.com/grain-lang/binaryen.ml/tree/phated/atomics - the blocker is that the binaryen.js wrapper makes the JS implementation bad (like BinaryenStore and BinaryenLoad)