Hi Kyrill, > This would make USE_NEW_VECTOR_COSTS effectively the default. > Jennifer has been trying to do that as well and then to remove it (as it > would be always true) but there are some codegen regressions that still > > need to be addressed.
Yes, that's the goal - we should use good tuning settings by default, especially if they work well on modern cores. I noticed a huge gap between -mcpu=neoverse-v2 and -march=armv9-a, so the idea is to make the tunings more similar. Note this particular patch won't make a difference since both of these tunings already use the new vector costs and throughput setting. > See the threads “[RFC][PATCH] AArch64: Remove > AARCH64_EXTRA_TUNE_USE_NEW_VECTOR_COSTS” from October and September. > Do those regressions go away if you also specify > AARCH64_EXTRA_TUNE_MATCHED_VECTOR_THROUGHPUT at the same time? I believe we always use both of those settings together. Removing the settings by making them the default looks like a good idea indeed. We have too many tune settings... Cheers, Wilco
