Hi Sebastian, I presume you're trying to unify the --with- options across most targets? That would be very useful! However there are significant differences between targets in how they interpret options like --with-arch=native (or -march). So those differences also need to be looked at and fixed to avoid unexpected results.
As for the first patch, I think support for --witch-tune requires more changes. Without proper processing of a --with-tune, you get an incorrect architecture version (if say the CPU you tune for is newer than the --with-cpu/arch or default). I posted patches to add --with-tune and fix various issues a while back: https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553865.html https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553866.html So I think these should go in first. They are simple and useful enough to backport (since they fix bugs) but that decision is up to the AArch64 maintainers. As for your second patch, --with-cpu-64 could be a simple alias indeed, but what is the exact definition/expected behaviour of a --with-cpu-32 on a target that only supports 64-bit code? The AArch64 target cannot generate AArch32 code, so we shouldn't silently accept it. Cheers, Wilco
