Handle memref type function arguments/returns #28
Description
When we compile a function with memref type arguments or returns, existing pipeline (LLVM IR -> wasm) produces a wasm function with multiple arguments, which corresponds to the input address of the memref data and also strides.
My current implementation only takes one argument, which is the address of the input, and does not take strides as arguments.
In any case, the caller is responsible for setting the strides correctly, so I'm not really sure if we should fix this.