Skip to content

Releases

Perimortem 0.6.0

Choose a tag to compare

@MatthewKaes MatthewKaes released this 04 Nov 02:31

Perimortem 0.6.0 adopts Toolchain 0.7.1 and unifies project setup and release packaging.

  • Declare the component graph and source builds in one root BUILD file.
  • Install shared Bazel and VS Code settings with :setup.
  • Use compiler AVX2 detection and the standard NDEBUG macro.
  • Preserve Windows allocation behavior and portable diagnostic-path checks.
  • Package static and shared SDKs for Linux, Windows and Web through :sdk.

Validated with 416 Windows Debug tests, 415 optimized Windows tests and 386 Web tests with one expected native-library skip. Independent static and shared Windows SDK consumers compiled and ran after relocation. Linux SDKs were cross-built on Windows; native Linux execution was not performed in this release audit.

The source snapshot was produced from the clean tagged commit after the formatter, host tests and SDK packaging passed.

Perimortem 0.5.0

Choose a tag to compare

@MatthewKaes MatthewKaes released this 26 Oct 21:36

Perimortem 0.5.0 narrows the published Compression surface to Deflate and adopts Toolchain 0.5.0.

Main update:

Compression::Deflate remains the complete public codec API. BitStream, Huffman and Lz77 remain available to Perimortem's source build while Toolchain excludes their implementation headers from SDK archives and component metadata.

Features:

  • Publish compression and decompression through Compression::Deflate without exposing its bit-stream, Huffman or Lz77 machinery.
  • Keep the internal codec headers beside their implementations without adding a separate source tree or Bazel wrapper targets.
  • Package the reduced Compression component consistently across Linux, Windows and Web static/shared SDK variants.
  • Adopt Toolchain 0.5.0's private-header packaging and public-header dependency checks.
  • Run Web validation through the standard --config=web workflow with Perimortem's static runtime.
  • Preserve native validation through the shared runtime so missing exports remain visible before publication.

The 0.5.0 source hotpatch refreshes the Toolchain pin for repositories publishing multiple SDK modules. The SDK archives remain unchanged.

Perimortem 0.4.0

Choose a tag to compare

@MatthewKaes MatthewKaes released this 19 Oct 08:51

Perimortem 0.4.0 hardens the shared Tetrodotoxin runtime around explicit capability, lifetime and platform boundaries.

Main update:

Core values, allocated containers, serialization, diagnostics and host services now publish the invariants needed to use them safely across allocation policies, arenas, threads and SDK boundaries. The same runtime is packaged for native and Web consumers through Toolchain 0.4.1.

Features:

  • Organize Core around Algorithm, View, Access, Storage, Math, Reader, Writer, Diagnostics and Synchronization capabilities.
  • Separate Bytes, Vector, Map and Set behavior from Thread, Global and Managed storage policies, with explicit allocation and lifetime contracts.
  • Standardize safe View indexing and the get_view, get_access and side-effect-free try_access conventions.
  • Add shaped Matrix View, Access and inline Storage forms backed by Core Math domains, bounds and sizes.
  • Replace Worker transport policy with a focused native Thread primitive that provides naming, joining and portable failure reporting.
  • Add canonical filesystem Paths with captured root, temporary, home, working and executable anchors, plus Directory validation and File fingerprints.
  • Define Perimortem's compact JSON dialect, strict tree lifetimes, safe zero-state navigation and bounded formatting behavior.
  • Separate Serialization Formats, Encodings and Streams, with fixed-component Version values.
  • Harden Deflate input validation while keeping Huffman, Lz77 and bit-stream invariants local to the codec implementation.
  • Make diagnostic time, messages, sinks, attribution and synchronization explicit, including deterministic clipping and per-thread file routing.
  • Harden Philox thread seeding, native library lifecycle reporting and process argument extraction.
  • Run the native validation suite as a standalone WebAssembly program through the pinned Toolchain 0.4.1 Node runner.
  • Refresh SDK manifests with explicit static archive and whole-archive link requirements through the Toolchain 0.4.1 hotpatch.
  • Separate Core::Identity::Uuid values from UUID text conversion in Serialization::Formats::Uuid. System::Random generates Core identifiers, and System no longer requires Serialization.
  • Preserve the two-word perimortem_uuid C record. C++ callers use the Core value type and Serialization::Formats::Uuid::serialize(value) for text output.

Perimortem 0.3.0

Choose a tag to compare

@MatthewKaes MatthewKaes released this 01 Oct 23:13

Perimortem 0.3.0 packages the core runtime and utility library as static and shared SDKs, with component interfaces for Core, Utility, Math, Memory, Compression, Serialization, and System.

Changes since 0.1.0:

  • Build and package through Toolchain 0.3.0. Public headers live under source/perimortem, matching their include paths. Root build declarations use the shared library, package, tests, benchmarks, and vscode helpers.
  • Ship static and shared libraries for Linux, Windows, and WebAssembly. The compiled API and supported stream template instantiations have explicit exports. Windows archives distinguish the static library from the DLL import library.
  • Select component interfaces without exposing every Perimortem header. Components share the runtime while retaining their declared public header dependencies.
  • Remove the former TTX ABI adapters, Core::Object, Core::Implementation, descriptor binding, and the legacy Terminal wrapper. Perimortem's runtime no longer supplies those TTX-specific object and terminal interfaces.
  • Simplify Dynamic::Bytes and Dynamic::Record around direct storage. Bytes copies own independent storage, and writable access no longer triggers copy-on-write machinery. Remove the obsolete map laundering operation.
  • Separate geometry and storage from rendering: Math supplies points, sizes, boundaries, domains, and volumes; Memory supplies Matrix; PNG serialization uses Rgba8 samples. Rendering belongs to Photophore.
  • Require explicit bounds when converting C strings with NullTerminated::convert_cstring. Exact-length to_view conversions preserve embedded zero bytes.
  • Keep tests and benchmarks as standalone executables with working-directory fixture paths. Shared VS Code configuration supplies separate Debug and Release workflows.

The standard repository commands are:

bazel build ...
bazel run :tests
bazel run :benchmarks
bazel build :sdk --config=release
bazel run :vscode

The SDK target is excluded from wildcard builds. Requesting :sdk packages both linkage variants for all supported platforms, together with headers, source, component metadata, and checksums.

Existing consumers should update removed object/ABI interfaces, use Core::Scalar in place of Core::Math, and select the required SDK linkage and components. C_LINKAGE from toolchain/export.h replaces PERIMORTEM_C. Static consumers need PERIMORTEM_STATIC=1; Toolchain's SDK importer supplies it automatically. Shared consumers use the default import declarations.

End-to-end Windows validation remains outstanding.

Perimortem 0.1.0

Choose a tag to compare

@MatthewKaes MatthewKaes released this 27 Sep 21:50

Initial Perimortem SDK release.

Assets contain shared headers, source, and separate Linux x86-64-v3, Windows x64 MSVC ABI, and Emscripten Wasm32 libraries. Linux requires RDRAND and the glibc 2.35 baseline. Wasm libraries require their Emscripten host runtime.