Skip to content

Releases: mutable-org/mutable

v0.0.56

26 Jun 16:04
Compare
Choose a tag to compare
[Benchmark] Fix hyper timeout value

v0.0.55: [CMake] Fix missing build byproducts.

26 Jun 12:46
8afa846
Compare
Choose a tag to compare
Some build byproducts were missing or incorrect.  This lead to
build configuration errors for static library builds.

v0.0.54: [Binaryen] Update Binaryen to version 112.

26 Jun 10:58
5b5bf8c
Compare
Choose a tag to compare
With that update, `wasm::IString::operator bool()` was made `explicit`.
We therefore must explicitly convert the name to `bool`.

v0.0.53

20 Jun 15:03
56a4b09
Compare
Choose a tag to compare
[Eval] Add planner config `PEall` in eval script.

v0.0.52

19 Jun 16:46
Compare
Choose a tag to compare
[Benchmark] Adapt data generation of integer columns.

v0.0.51

16 Jun 05:05
Compare
Choose a tag to compare
[WasmDSL] Add `PrimitiveExpr::reinterpret()` and use it for floating …

v0.0.50: [Wasm] Fix emitting setup code too late.

14 Jun 00:20
Compare
Choose a tag to compare
Setup code should *always* be emitted before emitting of the own computation
code, e.g. the setup code must be emitted before compiling a data layout since
this compilation may temporarily introduce boolean variables and emit code
using them into the returned blocks, however, these blocks may be placed
between setup and teardown code which may represent the lifespan of another
boolean variable which then overrides the value of the other one (our DSL is
able to use the same bit again since the `Variable` object is already distroyed
and thus its bit is free to use).
We had this issue previously and thus introduced the `referenced_bits_` field
for `PrimitiveExpr`s, however, beeing able to return blocks of Wasm code and
place them somewhere else circumvents our former solution. Maybe we can extend
the idea of memorizing referenced bits to blocks as well until they are
attached or destroyed.

v0.0.49: [CMake] Fix Test env variables misinterpretation

07 Jun 07:50
04da96f
Compare
Choose a tag to compare
Changed setting test environment variables from single-line to
multi-line syntax. `detect_container_overflow` and `MallocNanoZone`
were not being applied, resulting to failure of Integration Tests
on apple ARM devices. Introduced same syntax for non-apple as well.

Support ARM64 Architecture

31 May 16:35
467c5bb
Compare
Choose a tag to compare
[UTest] Fix unit test assuming 4 KiB page size.

Fix the unit test of of `list_allocator`, which was incorrectly assuming
4 KiB pages. However, on macOS M1 (ARM architecture), we do have 16 KiB
pages. This fix adapts the pre-allocation to compute the amount of
memory based on the system's actual pagesize.

v0.0.47

31 May 10:21
9ed0d90
Compare
Choose a tag to compare
[Doc] Update important links in README.