xavi/nanowasm, branch masterThe tiny WebAssembly interpreter that does not block you.
https://gitea.privatedns.org/xavi/nanowasm/atom?h=master2026-02-16T17:46:06+00:00section.c: Remove debug log2026-02-16T17:46:06+00:00Xavier Del Campo Romeroxavi92@disroot.org2026-02-16T17:46:06+00:00urn:sha1:3f915cb9468ade6a3801bea5ecac08b488e2836a
This call to nwp_log was only meant for debugging purposes during
early versions of the library.
Add i32.xor2025-11-15T17:53:32+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-11-15T17:53:32+00:00urn:sha1:4e4964c65700636e7411ea2d83b7f25ca4ad1377Add select operator2025-11-15T17:53:12+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-11-15T17:53:12+00:00urn:sha1:6c2108e6bd19ffa47b33f61501f25db47ddb4cfbCheck memory linear accesses are within bounds2025-11-15T17:50:55+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-11-15T17:50:55+00:00urn:sha1:b1034b86023672e6750da49b01a7d429cd8339d0
WebAssembly defines how many pages of linear memory are owned by the
instance on startup. This limit can then be bumped via the grow_memory
operator.
Therefore, accesses outside the defined bounds are considered an
exception.
Add br_table2025-11-15T17:48:16+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-11-15T17:48:16+00:00urn:sha1:0b2a1fd9439d5ab1cdc076d7b9f1e763c4900b74
br_table is in fact a generalization of other branch types like br or
br_if, since br_table contains several branches for the same pc inside
the nw_lo section.
Therefore, this kind of branch forced some changes to nwp_break and
those relying on it.
Add nwp_type_str2025-11-15T17:45:20+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-11-15T17:44:47+00:00urn:sha1:4a356bf56051361f2c72037f4fb043f8fdaa576c
This private function allows to decode an enum nw_type to a
human-readable string.
Add i32.shr_{s,u}2025-11-12T23:57:36+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-11-12T23:57:36+00:00urn:sha1:ac1796a1281aa6a6c9da3e407cb871d321da9d6ccall_import.c: Fix prev_ret2025-11-11T23:35:04+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-11-11T23:35:04+00:00urn:sha1:c3d6bac9d716433ca31f7d39332b2a6a96d8187d
So far, this variable was only being assigned by unwind.c, which is
called only for WebAssembly functions. However, it is still mandatory
to report the last returned value from imported functions, too, as
prev_ret is relied upon by operators such as `drop`.
execute.c: Report exception also on repeated callback2025-11-11T23:33:40+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-11-11T23:33:40+00:00urn:sha1:be7c97ce6ae43d677b28d455506fdaedf944a25b
So far, exceptions coming from the pc callback were only being reported
on its first call. However, pc callbacks might assign a continuation
callback if the operation cannot be completed on a single call.
Fix prev_op2025-11-11T23:32:15+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-11-11T23:32:15+00:00urn:sha1:cf2882c2e754f49c46ce2ca12c3ca07e4cabc459
Assigning prev_op inside nwp_execute defeated the purpose because this
function is meant to start the state machine for the given instruction.
In other words, inspecting prev_op would in fact return the current
opcode, instead of the previous opcode.