Up to [cvs.NetBSD.org] / pkgsrc / devel / binaryen
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
*: replace CMAKE_ARGS with CMAKE_CONFIGURE_ARGS
binaryen: Optionize googletest dependency
binaryen: update to 116. v116 ---- - "I31New" changed to "RefI31" everywhere it appears in the C API and similarly "i31.new" has been replaced with "ref.i31" in the JS API and in printed output (#5930, #3931). - The standard WasmGC opcodes are now on by default (#5873). v115 ---- - The nonstandard, experimental gc-nn-locals feature has been removed now that standard non-nullable locals are supported. (#5080) - Print all debug annotations when `BINARYEN_PRINT_FULL`. (#5904) - Use the standard text format for WasmGC now that things are stable there. (#5894, #5889, #5852, #5801) - Rename multimemory flag to `--multimemory` to match its naming in LLVM. (#5890) - Allow opting into standard GC encodings at compile time. (#5868) - Remove legacy WasmGC instructions. (#5861) - GUFA: Infer using TrapsNeverHappen. (#5850) - Add a pass to reorder functions by name, which can be useful for debugging (e.g. comparisons after optimizations), `--reorder-functions-by-name`. (#5811) - C API: Add `BinaryenAddFunctionWithHeapType` which is like `BinaryenAddFunction` but takes a heap type. The old function is kept for backwards compatibility and as a convenience. (#5829) - Work on new optimization framework using lattices. (#5784, #5794, #5800, #5817, #5831, #5849) - Heap types are now final by default and openness must be opted into both in the text and binary formats as well as in the TypeBuilder API. (#5918)
*: recursive bump for Python 3.11 as new default
binaryen: update to 114. v114 ---- - Fix a bug where e.g. -O3 -Oz ran the -O3 with the opt levels of -Oz, which could inhibit inlining, for example. While this is a bugfix, it affects how commandline options are interpreted, so if you depended on the old behavior this may be a breaking change. That is, the old behavior made -O3 -Oz run the first -O3 with -Oz's opt levels, and the new behavior is to run -O3 with the proper (-O3) opt levels. - Add pass to remove Exception Handling instructions.
binaryen: update to 113. v113 ---- - Add a `wasm-merge` tool. This is a full rewrite of the previous `wasm-merge` tool that was removed from the tree in the past. The new version is much simpler after recent improvements to multi-memory and multi-table. The rewrite was motivated by new use cases for merging modules in the context of WasmGC. - Some C and JS API functions now refer to data and element segments by name instead of index. - The `--nominal` and `--hybrid` command line options and related API functions have been removed. The only supported type system is now the standard isorecursive (i.e. hybrid) type system. - Add a "mayNotReturn" effect. - Disable the memory64 feature in Memory64Lowering.cpp. - Disable sign extension in SignExtLowering.cpp.
binaryen: switch to cmake/build.mk
binaryen: update to 112. v112 ---- - Add AbstractTypeRefining pass (#5461) - Add a mechanism to skip a pass by name (#5448) - Add TypeMerging pass (#5321) - Add TypeSSA pass (#5299) - Optimization sequences like `-O3 -Os` now do the expected thing and run `-O3` followed by `-Os`. Previously the last of them set the defaults that were used by all executions, so `-O3 -Os` was equivalent to `-Os -Os`. (There is no change to the default optimization level that other passes can see. For example, `--precompute-propagate -O2 -O1` will run `--precompute-propagate` at opt level `1`, as the global default is set to `2` and then overridden to `1`. The only change is that the passes run by `-O2` will actually run `-O2` now, while before they'd use the global default which made them do `-O1`.) - Add `--closed-world` flag. This enables more optimizations in GC mode as it lets us assume that we can change types inside the module. - The isorecursive WasmGC type system (i.e. --hybrid) is now the default to match the spec and the old default equirecursive (i.e. --structural) system has been removed. - `ref.is_func`, `ref.is_data`, and `ref.is_i31` have been removed from the C and JS APIs and `RefIs` has been replaced with `RefIsNull`. - Types `Data` and `Dataref` have been replaced with types `Struct` and `Structref` in the C and JS APIs. * `BinaryenStringNew` now takes an additional last argument, `try_`, indicating whether the instruction is one of `string.new_utf8_try` respectively `string.new_utf8_array_try`. * `BinaryenStringEq` now takes an additional second argument, `op`, that is either `BinaryenStringEqEqual()` if the instruction is `string.eq` or `BinaryenStringEqCompare()` if the instruction is `string.compare`.
binaryen: update to 111. v111 ---- - Add extra `memory64` argument for `BinaryenSetMemory` and new `BinaryenMemoryIs64` C-API method to determine 64-bit memory. (#4963) - `TypeBuilderSetSubType` now takes a supertype as the second argument. - `call_ref` now takes a mandatory signature type immediate. - If `THROW_ON_FATAL` is defined at compile-time, then fatal errors will throw a `std::runtime_error` instead of terminating the process. This may be used by embedders of Binaryen to recover from errors. - Implemented bottom heap types: `none`, `nofunc`, and `noextern`. RefNull expressions and null `Literal`s must now have type `nullref`, `nullfuncref`, or `nullexternref`. - The C-API's `BinaryenTypeI31ref` and `BinaryenTypeDataref` now return nullable types. - The `sign-extension` and `mutable-globals` features are now both enabled by default in all tools. This is in order to match llvm's defaults (See https://reviews.llvm.org/D125728). - Add a pass to lower sign-extension operations to MVP.
*: drop maintainership for WebAssembly related packages.
binaryen: update to 110. v110 ---- - Add support for non-nullable locals in wasm GC. - Add support for multiple memories. - Add support for the wasm Strings proposal. (see PRs with [Strings] in name) - Add a new flag to Directize, `--pass-arg=directize-initial-contents-immutable` which indicates the initial table contents are immutable. That is the case for LLVM, for example, and it allows us to optimize more indirect calls to direct ones. - Change constant values of some reference types in the C and JS APIs. This is only observable if you hardcode specific values instead of calling the relevant methods (like `BinaryenTypeDataref()`). - `BinaryenModulePrintStackIR`, `BinaryenModuleWriteStackIR` and `BinaryenModuleAllocateAndWriteStackIR` now have an extra boolean argument `optimize`. - Remove support for the `let` instruction that has been removed from the typed function references spec. - HeapType::ext has been restored but is no longer a subtype of HeapType::any to match the latest updates in the GC spec. - `i31ref` and `dataref` are now nullable to match the latest GC spec. - Add support for `extern.externalize` and `extern.internalize`.
binaryen: update to 109. v109 ---- - Add Global Struct Inference pass (#4659) (#4714) - Restore and fix SpillPointers pass (#4570) - Update relaxed SIMD instructions to latest spec
binaryen: update USE_LANGUAGES, it now uses c++17.
binaryen: update to 108. v108 ---- - Add CMake flag BUILD_TOOLS to control building tools (#4655) - Add CMake flag JS_OF_OCAML for js_of_ocaml (#4637) - Remove externref (#4633)
binaryen: update to 107. v107 ---- - Update the wasm GC type section binary format (#4625, #4631) - Lift the restriction in liveness-traversal.h on max 65535 locals (#4567) - Switch to nominal fuzzing by default (#4610) - Refactor Feature::All to match FeatureSet.setAll() (#4557) - New Signature Pruning pass (#4545) - Add support for extended-const proposal (#4529) - Add BUILD_TESTS CMake option to make gtest dependency optional. - Updated tests to use filecheck 0.0.22 (#4537). Updating is required to successfully run the lit tests. This can be done with `pip3 install -r requirements-dev.txt`.
binaryen: update to 106. v106 ---- - [wasm2js] Support exports of Globals (#4523) - MergeSimilarFunctions optimization pass (#4414) - Various wasm-ctor-eval improvements, including support for GC.
binaryen: update to 105. v105 --- - This release contains binaries for ARM64 MacOS devices (#4397) - Otherwise, mostly bug fixes and incremental optimization improvements.
binaryen: update to 104. v104 ---- - Bugfixes only, release created due to incorrect github release artifacts in v103 release (#4398).
binaryen: update to 103. v103 ---- - The EffectAnalyzer now takes advantage of immutability of globals. To achieve that it must have access to the module. That is already the case in the C++ API, but the JS API allowed one to optionally not add a module when calling `getSideEffects()`. It is now mandatory to pass in the module. - JS and Wasm builds now emit ECMAScript modules. New usage is: ```js import Binaryen from "path/to/binaryen.js"; const binaryen = await Binaryen(); ... ``` - CallIndirect changed from storing a Signature to storing a HeapType
binaryen: update to 102. v102 ---- - Add `BinaryenUpdateMaps` to the C API. - Adds a TrapsNeverHappen mode (#4059). This has many of the benefits of IgnoreImplicitTraps, but can be used safely in more cases. IgnoreImplicitTraps is now deprecated. - Adds type argument for BinaryenAddTable method (#4107). For the binaryen.js api this parameter is optional and by default is set to funcref type. - Replace `BinaryenExpressionGetSideEffects`'s features parameter with a module parameter.
binaryen: update to 101.
v101
----
- `BinaryenSetFunctionTable` and `module.setFunctionTable` have been removed
in favor of `BinaryenAddTable` and `module.addTable` respectively.
- `BinaryenIsFunctionTableImported` is removed.
- A new type `BinaryenElementSegmentRef` has been added to the C API with
new apis in both C & JS:
- `BinaryenAddActiveElementSegment`
- `BinaryenAddPassiveElementSegment`
- `BinaryenRemoveElementSegment`
- `BinaryenGetElementSegment`
- `BinaryenGetElementSegmentByIndex`
- `BinaryenElementSegmentGetName`
- `BinaryenElementSegmentSetName`
- `BinaryenElementSegmentGetTable`
- `BinaryenElementSegmentSetTable`
- `BinayenElementSegmentIsPassive`
- `module.addActiveElementSegment`
- `module.addPassiveElementSegment`
- `module.removeElementSegment`
- `module.getElementSegment`
- `module.getElementSegmentByIndex`
- `module.getTableSegments`
- `module.getNumElementSegments`
- `binaryen.getElementSegmentInfo`
- `BinaryenAddTable` and `module.addTable` no longer take offset and function
names.
- `BinaryenGetNumFunctionTableSegments` is replaced with
`BinaryenGetNumElementSegments`.
- `BinaryenGetFunctionTableSegmentOffset` is replaced with
`BinaryenElementSegmentGetOffset`.
- `BinaryenGetFunctionTableSegmentLength` is replaced with
`BinaryenElementSegmentGetLength`.
- `BinaryenGetFunctionTableSegmentData` is replaced with
`BinaryenElementSegmentGetData`.
- Boolean values in the C API now should use `bool` instead of `int`.
- Experimental SIMD instructions have been removed and the names and opcodes of
the standard instructions have been updated to match the final spec.
binaryen: update to 100. v100 ---- - `wasm-dis` now supports options to enable or disable Wasm features. - Reference types support has been improved by allowing multiple tables in a module. - `call_indirect` and `return_call_indirect` now take an additional table name parameter. This is necessary for reference types support. - New getter/setter methods have been introduced for `call_indirect` table name: - `BinaryenCallIndirectGetTable` - `BinaryenCallIndirectSetTable` - JS API `CallIndirect.table` - New APIs have been added to add and manipulate multiple tables in a module: - `BinaryenAddTable` - `BinaryenRemoveTable` - `BinaryenGetNumTables` - `BinaryenGetTable` - `BinaryenGetTableByIndex` - `BinaryenTableGetName` - `BinaryenTableGetInitial` - `BinaryenTableHasMax` - `BinaryenTableGetMax` - `BinaryenTableImportGetModule` - `BinaryenTableImportGetBase` - `module.addTable` - `module.removeTable` - `module.getTable` - `module.getTableByIndex` - `module.getNumTables` - `binaryen.getTableInfo`
devel/binaryen: import binaryen-99. Binaryen is a compiler and toolchain infrastructure library for WebAssembly, written in C++. It aims to make compiling to WebAssembly easy, fast, and effective. * Easy: Binaryen has a simple C API in a single header, and can also be used from JavaScript. It accepts input in WebAssembly-like form but also accepts a general control flow graph for compilers that prefer that. * Fast: Binaryen's internal IR uses compact data structures and is designed for completely parallel codegen and optimization, using all available CPU cores. Binaryen's IR also compiles down to WebAssembly extremely easily and quickly because it is essentially a subset of WebAssembly. * Effective: Binaryen's optimizer has many passes (see an overview later down) that can improve code size and speed. These optimizations aim to make Binaryen powerful enough to be used as a compiler backend by itself. One specific area of focus is on WebAssembly-specific optimizations (that general-purpose compilers might not do), which you can think of as wasm minification, similar to minification for JavaScript, CSS, etc., all of which are language-specific.