arm builds

[johnnynunez]

https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/

Digits, jetson thor, cuda arm laptops are coming

windows arm q2 2025: github/roadmap#1098

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.01%. Comparing base (914aeec) to head (c589ebd).

Additional details and impacted files

@@           Coverage Diff           @@
##            devel    #2949   +/-   ##
=======================================
  Coverage   91.01%   91.01%           
=======================================
  Files         198      198           
  Lines        8599     8599           
=======================================
  Hits         7826     7826           
  Misses        773      773           

[ChrisThrasher]

In my experience, unless you're doing exotic things like using compiler intrinsics and inline assembly, CPU architecture is a non-factor in how I write and test my C++ code. What types of errors do you think these new jobs will catch that the existing CI jobs will not catch?

[johnnynunez]

In my experience, unless you're doing exotic things like using compiler intrinsics and inline assembly, CPU architecture is a non-factor in how I write and test my C++ code. What types of errors do you think these new jobs will catch that the existing CI jobs will not catch?

Because in H2 a lot of arm devices are coming... (cuda laptops, digits etc)

[ChrisThrasher]

I'm afraid that doesn't really answer my question. The computer hardware market is already full of ARM devices thanks to Apple. I've been using Catch2 on an ARM device for many years. What kinds of errors would these ARM jobs catch that the existing x86 jobs would not catch? My point is that the existing CI pipeline may already be sufficient but I might be missing some of the value of the jobs you added.