Adam Reichold 6fcac11bc6 Make clearing value stack between export invocations optional ... This avoids the main overhead of repeated export invocations by making it optional to clear the value stack after each interpreter run. This is especially useful if different exports of the same module are invoked repeated so that no unintended information leaks are possible.		2019-06-18 16:47:19 +02:00
..
bin	rustfmt (#151)	2018-12-11 12:54:06 +01:00
prepare	fix(compile module): remove unused `mut` (#179)	2019-05-03 14:46:01 +01:00
tests	Check type when resuming function (#152)	2019-01-02 12:18:24 +01:00
func.rs	Recycle value stacks to avoid allocation costs (#184)	2019-06-12 10:51:04 +02:00
global.rs	rustfmt (#151)	2018-12-11 12:54:06 +01:00
host.rs	rustfmt (#151)	2018-12-11 12:54:06 +01:00
imports.rs	Remove hashbrown and use BTree{Map,Set} from the alloc crate (#187)	2019-06-12 11:30:10 +02:00
isa.rs	Extract validation into a separate crate (#176)	2019-04-19 16:05:09 +02:00
lib.rs	Add ARMv7 as CI test target (#186)	2019-06-18 15:06:16 +02:00
memory.rs	Replaced std with core in the TryInto import (#181)	2019-05-16 18:46:22 +02:00
module.rs	Remove hashbrown and use BTree{Map,Set} from the alloc crate (#187)	2019-06-12 11:30:10 +02:00
nan_preserving_float.rs	Extract validation into a separate crate (#176)	2019-04-19 16:05:09 +02:00
runner.rs	Make clearing value stack between export invocations optional	2019-06-18 16:47:19 +02:00
table.rs	Extract validation into a separate crate (#176)	2019-04-19 16:05:09 +02:00
types.rs	rustfmt (#151)	2018-12-11 12:54:06 +01:00
value.rs	Add ARMv7 as CI test target (#186)	2019-06-18 15:06:16 +02:00