I’m writing compiled apps to run on performance Machines and I would obviously like to make use of vectorized instructions as much as possible. This post is a feature request for Fly to provide a guarantee about the oldest microarchitectures used currently by the Fly servers, and the oldest microarchitectures that will be used in future. For example, if I knew that all the Fly servers now and in future will be post–Sandy Bridge and post-Bulldozer, I could enable AVX.
Ideally, this information would be published and kept up-to-date somewhere in the Fly documentation, but a reply here is fine as well :）
It would also be nice to have Fly’s default templates for e.g. Rust enable the appropriate features via -C target-feature=… flags.