Repository navigation
CrossPascal Early Access 014
Pre-releaseThis update speeds up model-file verification in Windows Delphi builds. Delphi and Lazarus now use the same Windows SHA-256 implementation and still verify every byte of the model files.
On the checked Qwen2.5 1.5B bundle, Delphi verification fell from about 46 seconds to 4 seconds. A short first answer fell from about 52 seconds to 10 seconds in the warm-file-cache comparison. A fresh installed Lazarus run after a host restart took about 18 seconds, including 12 seconds reading and verifying the weights. These measurements are not guarantees for other storage devices or models.
Delphi 13.2 and Lazarus 4.8 builds passed. The supplied executable files are built with Lazarus only. The model converter, weights, compiled TVM graphs, native runtime, and supported feature scope are unchanged from Early Access 013.
For a matched 32-token FP32 test, Delphi, Lazarus, and Python + TVM took about 6-7 seconds per answer. PyTorch took about 1.8 seconds for its first answer and 1 second for the second. All output token IDs matched. Keep a model loaded to avoid repeating file verification and GPU upload.
Extract crosspascal-windows-x64-ea014.zip and the unchanged crosspascal-gemma-runtime-windows-x64-ea013.zip into the same parent folder. The EA008 OpenCV, Leptonica, and CPU-model source archives are unchanged. Model weights are not included.
This is a Early Access release. Existing experimental model and image-profile restrictions continue to apply.
Documentation update - 9 November 2026
The accompanying README files, setup guides and preparation helper use the public-download workflow. SHA-256 inventories were refreshed for these revised packages. Model weights and inference binaries are unchanged. Existing Git tags retain the original code baseline; current setup guidance is maintained in the default branches.
Packaging maintenance, 10 November 2026
Source documentation and integrity inventories were refreshed. Runtime packaging changes affect documentation and integrity records. Model weights and the executable files in these historical packages are unchanged. The original Git tag and the scope of the model results are retained.