| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
apply memory segments only if there isn't a memory initializer (which we need for asmjs and asm2wasm modes)
use wasm-opt to check recreated wasts for validity, as wasm-shell would try to execute them
add testing for combined modes like asmjs,interpret-binary
|
| |
|
| |
|
|
|
|
|
|
| |
is not yet valid
then after finalizeCalls, we must autodrop again to drop things that finalizeCalls changed
|
|
|
|
| |
invalidate the branch
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
dropped
|
| |
|
| |
|
| |
|
|
|
|
| |
contents
|
| |
|
| |
|
| |
|
|
|
|
| |
the asm.js context informed us. this lets us add drops where necessary
|
| |
|
|
|
|
| |
consistent with refering to other global objects; e.g. this avoids ordering issues with imported vs non-imported globals
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
lines
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|