| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
This handles the case where WASM_BIGINT is enabled by default by emcc.
Binaryen's JS bindings do not currently work with bigint (see #7163)
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Specified at
https://github.com/WebAssembly/half-precision/blob/main/proposals/half-precision/Overview.md
|
| |
|
|
|
|
|
| |
Fixes https://github.com/emscripten-core/emscripten/issues/17228
This seems the right default in binaryen.js which is used as a library through
npm mostly. We aren't a main program that wants to control node exclusively.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This makes several changes to make the Emscripten build more configurable and
convenient for testing:
1) Remove ERROR_ON_WASM_CHANGES_AFTER_LINK from ENABLE_BIGINT: this makes the
setting composable with optimized builds
2) Add EMSCRIPTEN_ENABLE_MEMORY64 to build with the memory64 option
3) Add EMSCRIPTEN_ENABLE_SINGLE_FILE to allow disabling the single-file build
(to make it easier to analyze binary output)
|
| |
|
| |
This list is identical to `binaryen_SOURCES` above.
|
| | |
|
| |
|
|
| |
Emscripten had started complaining about the repeated NODERAWFS arguments in the
link command, but they would be nontrivial to deduplicate.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
No changes here to binaryen.js/wasm builds.
1. Add a flag to enable pthreads.
2. Use SINGLE_FILE on binaryen.js/.wasm as before, which is nice for library users
as they want just a single file to distribute for Binaryen support. For other builds
like wasm-opt.js etc. no longer set SINGLE_FILE, as that type of build wants to be
a replacement for a normal wasm-opt build as much as possible, so avoid the
overhead of SINGLE_FILE.
(Previously we disabled SINGLE_FILE also in the case of BUILD_FOR_BROWSER
but I don't think we need to special-case that any more.)
|
| |
|
|
|
| |
allocateUTF8OnStack (#6324)
This avoids a warning on recent Emscripten.
|
| |
|
| |
Emscripten sets that itself these days.
|
| |
|
|
|
|
| |
* No `SINGLE_FILE` when building for browser
* Ensure `STACK_SIZE` is big enough
* Fix indentation
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Class template argument deduction (CTAD) is a C++17 feature that allows
variables to be declared with class template types without specifying the
template parameters. Deduction guides are a mechanism by which template authors
can control how the template parameters are inferred when CTAD is used. The
Google style guide prohibits the use of CTAD except where template authors opt
in to supporting it by providing explicit deduction guides. For compatibility
with users adhering to Google style, set the compiler flag to check this
condition and add the necessary deduction guides to make the compiler happy
again.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Replace the static assertions ensuring that Lattice types have the necessary
operations with a C++20 concept called `Lattice`. To avoid name conflicts with
the new concept, rename existing type parameters named `Lattice` to `L`. When
not building with C++20, `Lattice` is a macro that resolves to `typename` so the
code continues compiling and has the same behavior, but without any eager checks
of the requirements on lattices.
Add a new C++20 builder to CI to ensure that future changes compile with both
C++17 and C++20. Once we switch to C++20 by default, the new builder can be
removed. Update the lint builder to use a recent clang-format that understands
concepts.
|
| |
|
|
|
|
| |
And put the new files in a new source directory, "parser". This is a rough split
and is not yet expected to dramatically improve compile times. The exact
organization of the new files is subject to change, but this splitting should be
enough to make further parser development more pleasant.
|
| |
|
| |
The important included change is the switch to default GC opcodes.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a new "analysis" source directory that will contain the source for a new
static program analysis framework. To start the framework, add a CFG utility
that provides convenient iterators for iterating through the basic blocks of the
CFG as well as the predecessors, successors, and contents of each block.
The new CFGs are constructed using the existing CFGWalker, but they are
different in that the new utility is meant to provide a usable representation of
a CFG whereas CFGWalker is meant to allow collecting arbitrary information about
each basic block in a CFG.
For testing and debugging purposes, add `print` methods to CFGs and basic
blocks. This requires exposing the ability to print expression contents
excluding children, which was something we previously did only for StackIR.
Also add a new gtest file with a test for constructing and printing a CFG. The
test reveals some strange properties of the current CFG construction, including
empty blocks and strange placement of `loop` instructions, but fixing these
problems is left as future work.
|
| |
|
|
| |
CMake defaults to -O3 to release builds. We were overriding that to
-O2 in general and re-overriding back to -O3 for emscripten.
|
| |
|
| |
Fixes #5647
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This should unbreak the build. This is an old problem but was just noticed due to
a recent emscripten change (emscripten-core/emscripten#18292).
|
| |
|
| |
This helps cut the size and build time of the emsdk package.
|
| |
|
| |
This better reflects what it really means. Also declare it with option()
|
| |
|
| |
This workaround is no longer needed after commit emscripten-core/emscripten@ce4c405.
|
| | |
|
| |
|
|
| |
This should make the CI green again. Also fix one of the errors. I haven't fixed
the other errors because I don't know how.
|
| | |
|
| | |
|
| |
|
|
|
| |
When building Binaryen to wasm in debug mode,
1) Avoid post-link Binaryen changes with WASM_BIGINT and by avoiding O3
2) Don't use SINGLE_FILE, to make it easier to analyze the resulting wasm
|
| | |
|
| |
|
|
|
| |
Avoid space between the `-s` and the option name and add `=` between
option name and value. This is better, especially for cmake where
some types of flags/options do no preserve order.
|
| |
|
| |
Also document minimal requirements for binaryen.js
|
| |
|
|
| |
binaryen.js uses allocate, which is no longer exported by default in emscripten
tip of tree builds.
|
| | |
|
| |
|
|
|
|
| |
Also, add `-Wl,--no-undefined` when linking shared libraries. Adding
this flags means we can better detect when libraries are missing from the
`libbinaryen.so` link. In this case it reports undefined symbol for
`pthread_create` (which is then addressed by this patch).
|
| |
|
|
|
| |
Line 167 in CMakeLists.txt causes libraries to be put into `/lib`.
Line 110, before this patch, causes binaries to look for libraries in `/${CMAKE_INSTALL_LIBDIR}`. This works out if CMAKE_INSTALL_LIBDIR equals `/lib`, which is the case on non-Linux and on Debian, see https://gitlab.kitware.com/cmake/cmake/-/blob/master/Modules/GNUInstallDirs.cmake#L221. On non-Debian Linux systems, however, it causes dynamic linking to fail unless `export LD_LIBRARY_PATH=/path/to/binaryen/lib` is manually set in the shell (or a `lib64 ->lib` symlink is created inside the Binaryen checkout). This patch fixes the inconsistency by putting `/lib` as the library search path into the created binaries.
(I suppose an alternative fix would be to update lines 167/168 to use `${CMAKE_INSTALL_LIBDIR}` instead, not sure if that would be preferable.)
|
| | |
|
| | |
|
| | |
|
| | |
|
