Using -march=native with gcc or -DARCH=native with cmake can make binaries which are a bit faster for your specific CPU architecture, but they also are more likely to not work on older CPU's. We don't want to use this option for release binaries, which we want to work on as many computers as possible, but it would be nice to have build.sh look for an env var to decide whether to use a native compile. This allows people who compile their own binaries to make them faster for themselves.
Using -march=native with gcc or -DARCH=native with cmake can make binaries which are a bit faster for your specific CPU architecture, but they also are more likely to not work on older CPU's. We don't want to use this option for release binaries, which we want to work on as many computers as possible, but it would be nice to have build.sh look for an env var to decide whether to use a native compile. This allows people who compile their own binaries to make them faster for themselves.
Using -march=native with gcc or -DARCH=native with cmake can make binaries which are a bit faster for your specific CPU architecture, but they also are more likely to not work on older CPU's. We don't want to use this option for release binaries, which we want to work on as many computers as possible, but it would be nice to have build.sh look for an env var to decide whether to use a native compile. This allows people who compile their own binaries to make them faster for themselves.