[us-commits] [ehb54/ultrascan3] b5ce2a: somo/grpy: ship the C++ GRPY binaries in add_to_bin

[emre brookes]

  Branch: refs/heads/ehb54-issue-1012
  Home:   https://github.com/ehb54/ultrascan3
  Commit: b5ce2aef6cda513b72da78eaa2bc4512e70dfcb5
      https://github.com/ehb54/ultrascan3/commit/b5ce2aef6cda513b72da78eaa2bc4512e70dfcb5
  Author: ehb54 <brookes at uthscsa.edu>
  Date:   2026-08-17 (Mon, 17 Aug 2026)

  Changed paths:
    M us_somo/add_to_bin/GRPY_linux64
    M us_somo/add_to_bin/GRPY_osx10.11
    M us_somo/add_to_bin/GRPY_win64.exe

  Log Message:
  -----------
  somo/grpy: ship the C++ GRPY binaries in add_to_bin

Replaces the Fortran GRPY binaries with builds of ehb54/grpy-cpp, under the same names, so
the lookup, add_to_bin and linux.pl all keep working untouched. Without this the branch
calls the program it always called and none of the port's work reaches a user.

  GRPY_osx10.11    universal x86_64 + arm64, ad-hoc signed. The Fortran binary was x86_64
                   only, so every Apple Silicon Mac was running GRPY under Rosetta.
  GRPY_linux64     fully static, as its predecessor was: no glibc floor. Threading checked
                   under -static (67.1 s on 1 thread vs 2.81 s on 32 at 1200 beads).
  GRPY_win64.exe   cross-compiled with mingw-w64, imports only KERNEL32 and the UCRT stubs.

The macOS and Linux binaries pass the full golden suite against the original Fortran output
at worst relative error 0.00e+00. THE WINDOWS BINARY HAS NOT BEEN RUN -- no Windows machine
or wine was reachable from any build host -- so it needs a smoke test on Windows before
this branch ships. Everything else about it is verified statically only.

What a user gets that the Fortran binaries could not give: threading, single precision,
out-of-core, and native arm64.

Refs ehb54/ultrascan-tickets#1012



To unsubscribe from these emails, change your notification settings at https://github.com/ehb54/ultrascan3/settings/notifications