Hi Richard, > I share Richard E's concern about the effect of this on people who run > ./cc1 directly. (And I'm being selfish here, because I regularly run > ./cc1 directly on toolchains configured with --with-arch=armv8.2-a+sve.) > So TBH my preference would be to keep the TARGET_CPU_DEFAULT_FLAGS stuff.
And what exactly should it do? It didn't work correctly before, and even now it's not clear what TARGET_CPU_DEFAULT should be set to for all possible combinations of --with-cpu=X --with-arch=Y --with-tune=Z. Should it have exactly the same behaviour with and without the driver? If so, that's difficult to achieve in config.gcc, and it would require a completely different mechanism to ensure the default ends up the same without the driver (eg. store the original strings in TARGET_CPU_DEFAULT and then postprocess in the backend as if they were actual --cpu/--arch/--tune commands if the command-line didn't already set them, ie. replicating what the driver already does). And it would need to be done for --with-abi as well. So is changing your preferred config to --with-cpu=neoverse-v1 really a problem? Cheers, Wilco
