forks/binaryen.git -

	Commit message (Collapse)	Author	Age	Files	Lines
*	wasm2js: Stop emitting nan and infinity (#5391)	Will Cohen	2023-01-04	1	-2/+0
\| \| \| \| \| \| \|	As noted in #4739, legacy language emitting nan and infinity exists, with the observation that it can be removed once asm.js is no longer used and global NaN is available. This commit removes that asm.js-specific code accordingly.
*	wasm2js: Support for flexible module import naming (#5114)	Sam Clegg	2022-10-05	1	-2/+1
\| \| \| \| \| \| \| \|	The previous code was making emscripten-specific assumptions about imports basically all coming from the `env` module. I can't find a way to make this backwards compatible so may do a combined roll with the emscripten-side change: https://github.com/emscripten-core/emscripten/pull/17806
*	wasm2js: Don't assume that `env.abort` can always be impored. (#5049)	Sam Clegg	2022-09-16	1	-3/+2
\| \| \| \| \| \|	This import was being injected and then used to implement trapping. Rather than injecting an import that doesn't exist in the original module we instead use the existing mechanism to implement this as an internal helper.
*	wasm2js: Have instantiate function take standard import object (#5018)	Sam Clegg	2022-09-14	1	-1/+2
\| \| \| \| \| \| \| \| \| \| \|	Previously we were assuming asmLibraryArg which is what emscripten passes as the `env` import object but using this method is more flexible and should allow wasm2js to work with import that are not all form a single object. The slight size increase here is just temporary until emscripten gets updated. See https://github.com/emscripten-core/emscripten/pull/17737
*	[wasm2js] Use native JavaScript Math.trunc (#3329)	Max Graey	2020-11-10	1	-0/+1
\|
*	wasm2js: Remove global dict arguments to asmFunc (#3325)	Sam Clegg	2020-11-05	1	-26/+13
\|
*	wasm2js: Skip heap creation in the absence of wasm memory. NFC (#3167)	Sam Clegg	2020-09-24	1	-11/+16
\| \| \| \| \|	Also, format the asmFunc call to make it more readable in the ES6 modules case.
*	wasm2js: coerce function pointer indexes (#2979)	Alon Zakai	2020-07-22	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	We emit FUNCTION_TABLE[ptr], where FUNCTION_TABLE is a JS array. That is a rare case where true is handled differently than 1 (a typed array or an add would cast, etc.), so we must explicitly cast there. Fixes an issue that existed before, but became a problem due to #2869 which optimized some selects into a form that emitted a true or a false, and if that was a function pointer, it could be bad, see https://app.circleci.com/pipelines/github/emscripten-core/emscripten/6699/workflows/0c4da49c-75d0-4b0a-8fac-686a8330a3fe/jobs/336520 The new test/wasm2js/indirect-select.2asm.js.opt output shows what happened there. Verified as passing emscripten's wasm2js1 wasm2js2 test suites.
*	Stop emitting "almost asm" in wasm2js output (#2221)	Alon Zakai	2019-07-12	1	-1/+0
\| \| \|	We don't ever emit "use asm" anymore, so this similar annotation is not really useful, it just increases size.
*	wasm2js: optimize away unneeded load coercions (#2107)	Alon Zakai	2019-05-15	1	-0/+1
\|
*	wasm2js: precompute bitwise operations (#2101)	Alon Zakai	2019-05-13	1	-3/+3
\| \| \|	This happens on e.g. an i32 load of a constant offset, then we have constant >> 2.
*	wasm2js: optimize loads (#2085)	Alon Zakai	2019-05-03	1	-1/+0
\| \| \| \|	When loading a boolean, prefer the signed heap (which is more commonly used, and may be faster). We never use HEAPU32 (HEAP32 is always enough), just remove it.
*	wasm2js: run full optimizations during the pipeline (#2071)	Alon Zakai	2019-04-30	1	-0/+49
	We flatten for the i64 lowering etc. passes, and it is worth optimizing afterwards, to clean up stuff they created. That is run if the user ran wasm2js with an optimization level (like wasm2js -O3). Split the test files to check both optimized and unoptimized code.