forks/binaryen.git -

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add multivalue feature (#2668)	Thomas Lively	2020-02-27	1	-27/+10
\|
*	Use FeatureSet instead of FeatureSet::Feature(NFC) (#2562)	Heejin Ahn	2020-01-02	1	-2/+3
\| \| \| \| \|	This uses `FeatureSet` in place of `FeatureSet::Feature` when possible, making it possible for functions take a set of multiple features as one argument.
*	Add string parameter to WASM_UNREACHABLE (#2499)	Sam Clegg	2019-12-05	1	-1/+2
\| \| \| \| \|	This works more like llvm's unreachable handler in that is preserves information even in release builds.
*	Fix #2430 properly (#2449)	Alon Zakai	2019-11-18	1	-10/+10
\|
*	Cast to bool after bitwise operations, to avoid an MSVC warning (#2431)	Alon Zakai	2019-11-12	1	-10/+12
\| \| \| \|	Fixes #2430
*	Add initial support for anyref as an opaque type (#2294)	Jay Phelps	2019-08-20	1	-1/+9
\| \| \| \| \| \| \| \| \| \| \| \| \|	Another round of trying to push upstream things from my fork. This PR only adds support for anyref itself as an opaque type. It does NOT implement the full [reference types proposal](https://github.com/WebAssembly/reference-types/blob/master/proposals/reference-types/Overview.md)--so no table.get/set/grow/etc or ref.null, ref.func, etc. Figured it was easier to review and merge as we go, especially if I did something fundamentally wrong. *** I did put it under the `--enable-reference-types` flag as I imagine that even though this PR doesn't complete the full feature set, it probably is the right home. Lmk if not. I'll also be adding a few github comments to places I want to point out/question.
*	Initial tail call implementation (#2197)	Thomas Lively	2019-07-03	1	-2/+9
\| \| \| \| \| \| \| \| \| \| \|	Including parsing, printing, assembling, disassembling. TODO: - interpreting - effects - finalization and typing - fuzzing - JS/C API
*	Features C/JS API (#2049)	Thomas Lively	2019-05-17	1	-1/+0
\| \| \| \| \|	Add feature handling to the C/JS APIs. No features are enabled by default, so all used features will have to be explicitly enabled in order for modules to validate.
*	Add exception handling feature (#2083)	Heejin Ahn	2019-05-03	1	-1/+10
\| \| \|	This only adds the feature and its flag and not the instructions yet.
*	clang-tidy braces changes (#2075)	Alon Zakai	2019-05-01	1	-6/+12
\| \| \|	Applies the changes in #2065, and temprarily disables the hook since it's too slow to run on a change this large. We should re-enable it in a later commit.
*	Apply format changes from #2048 (#2059)	Alon Zakai	2019-04-26	1	-19/+31
\| \| \|	Mass change to apply clang-format to everything. We are applying this in a PR by me so the (git) blame is all mine ;) but @aheejin did all the work to get clang-format set up and all the manual work to tidy up some things to make the output nicer in #2048
*	Change default feature set to MVP (#1993)	Thomas Lively	2019-04-16	1	-0/+8
\| \| \| \| \|	In the absence of the target features section or command line flags. When there are command line flags, it is an error if they do not exactly match the target features section, except if --detect-features has been provided. Also adds a --print-features pass to print the command line flags for all enabled options and uses it to make the feature tests more rigorous.
*	Move features from passOptions to Module (#2001)	Thomas Lively	2019-04-12	1	-3/+3
\| \| \| \| \|	This allows us to emit a (potentially modified) target features section and conditionally emit other sections such as the DataCount section based on the presence of features.
*	Add feature options to emscripten metadata (#1982)	Thomas Lively	2019-04-05	1	-0/+25
\| \| \|	Emscripten runs wasm-emscripten-finalize before running wasm-opt, so the target features section is stripped out before optimizations are run. One option would have been to add another wasm-opt invocation at the very end to strip the target features section, but dumping the features as metadata avoids the extra tool invocation. In the long run, it would be nice to have only as single binaryen invocation to do all the work that needs doing.
*	Use target features section in wasm-opt (#1967)	Thomas Lively	2019-04-03	1	-0/+5
\| \| \| \| \| \| \|	If the user does not supply features explicitly on the command line, read and use the features in the target features section for validation and passes. If the user does supply features explicitly, error if they are not a superset of the features marked as used in the target features section and the user does not explicitly handle this.
*	Validate that types match features (#1949)	Thomas Lively	2019-03-18	1	-0/+70
	Refactors features into a new wasm-features.h file and updates the validator to check that all types are allowed. Currently this is only relevant for the v128 SIMD type, but new types will be added in the future. The test for this change is in #1948.