Hi, >>> 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. >> >> IMO allowing users to specify all the flags available on x86 is important. >> > > This isn't about general users though; it's about how you configure the > compiler and that's not all the same. I don't mind the --with-cpu-64 as > a strict alias for --with-cpu, but --with-cpu-32 is both redundant and > misleading as it might give the impression that it does something useful.
We could make it do something useful, for example emit a warning, an error or default to -mabi=ilp32 (since that is similar to what other targets do). Anything is better than being the only target that doesn't support it... Cheers, Wilco
