wasmi

Commit Graph

Author	SHA1	Message	Date
Sergey Pepyakin	e273b9e40a	Just bump framestack limits. (#50 ) These limits seems to be picked arbitrary, and I just made it arbitrary larger. We need to reconsider these limits, ideally providing to user a way to customize the limits. FWIW, When the last time I've tried to run gcc's torture testsuite with wasmi it also bumped into this limit. Fixes #41.	2018-02-13 09:29:04 +03:00
Sergey Pepyakin	c0ed715b37	Update testsuite (#39 ) * ok_or_else in stack + top_mut. * Model polymorphic stack explicitly * Upgrade wasm testsuite. * Update fixtures. * Validate duplicate exports. * Fix and clean spec runner. * with_capcity for HashSet	2018-02-08 17:52:16 +03:00
Sergey Pepyakin	49347a63ee	Initial commit	2018-01-17 19:54:06 +03:00

Author

SHA1

Message

Date

Sergey Pepyakin

e273b9e40a

Just bump framestack limits. (#50 )

These limits seems to be picked arbitrary, and I just made it arbitrary larger.

We need to reconsider these limits, ideally providing to user a way to customize the limits.

FWIW, When the last time I've tried to run gcc's torture testsuite with wasmi it also bumped into this limit.

Fixes #41.

2018-02-13 09:29:04 +03:00

Sergey Pepyakin

c0ed715b37

Update testsuite (#39 )

* ok_or_else in stack + top_mut.

* Model polymorphic stack explicitly

* Upgrade wasm testsuite.

* Update fixtures.

* Validate duplicate exports.

* Fix and clean spec runner.

* with_capcity for HashSet

2018-02-08 17:52:16 +03:00

Sergey Pepyakin

49347a63ee

Initial commit

2018-01-17 19:54:06 +03:00

3 Commits