Skip to content

Releases: antmoev/bridct

Release list

BRiDCT dev.7 — source packages for macOS, Ubuntu and Windows

BRiDCT dev.7 — source packages for macOS, Ubuntu and Windows Pre-release
Pre-release

Choose a tag to compare

View all tags
@antmoev antmoev released this 25 Sep 14:58
v0.2.0-dev.7-r1
9766261

BRiDCT dev.7, accompanying arXiv:2609.28519v1, with standalone packaging revision r1.

Download the ZIP for macOS, Ubuntu or Windows, extract the whole archive and follow START_HERE.md. These are source packages with build/test launchers, not precompiled installers. They contain identical kernels and the same verification corpus.

  • Library: C11, orthonormal float32 DCT-II/inverse/round trip; independent power-of-two axes from 8 through 1024; Shao–Johnson throughout.
  • r1 changes documentation and distribution tooling only. The numerical implementation remains 0.2.0-dev.7; 111 implementation, generator, test and data files retain the paper snapshot's exact bytes.
  • The dataset ZIP is optional: the 474-input corpus is already included in every platform ZIP.
  • bridct-measurements.zip preserves the recorded paper data. It is separate from measurements made by running the launchers.
  • Original code: BSD-3-Clause. Verification data: CC BY 4.0. Preserve the included SIMDe/Ooura notices; Ooura is a benchmark comparator, not a library route.

Validation: local Apple Silicon C checks, 2,412 required independent numerical checks, the NumPy API across all 64 shapes, and Python lifecycle/hardening checks pass. Known boundary diagnostics remain separate. Fresh extracted-package GitHub validation passes on macOS ARM64, Ubuntu x86-64 and Windows x86-64. The Windows job runs the distributed launcher in verification mode. Each platform passes 2,412 required C checks and 1,152 NumPy numerical cases with two output contracts each; the 90 known failures among 162 boundary diagnostics remain explicitly separate.

CI checks builds and accuracy; shared-runner execution is not comparative performance evidence. MSVC, Linux ARM64 and Windows ARM are not validated by this release workflow. See docs/PLATFORMS.md for limits.

SHA256SUMS covers every attachment listed in it; RELEASE.json records the source commit and individual archive hashes. After extraction, python tools/verify_source.py verifies the package files and python dataset/verify.py verifies the input bytes (NumPy required).

Loading