On 11/19/20, 10:52 AM, "Richard Earnshaw (lists)" <richard.earns...@arm.com> wrote: > Having the same option have a completely different meaning would be even > worse than not having the option at all. So no, that's a non-starter.
The attached patch 0001 removes --with-{cpu,arch,tune}-32.
Bootstrap and regression testing pass on aarch64-linux.
Ok to commit to trunk and active branches?
I would like to ping the two patches from Wilco Dijkstra that fix issues in
configure --with-mtune flag:
https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553865.html
https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553866.html
Please see patches 0002 and 0003 attached, rebased on trunk as of today and
tested with bootstrap and regression testing.
Ok to commit to trunk and all active branches?
Thanks,
Sebastian
0001-AArch64-disable-with-cpu-arch-tune-32.patch
Description: 0001-AArch64-disable-with-cpu-arch-tune-32.patch
0002-AArch64-Cleanup-CPU-option-processing-code.patch
Description: 0002-AArch64-Cleanup-CPU-option-processing-code.patch
0003-AArch64-Add-support-for-with-tune.patch
Description: 0003-AArch64-Add-support-for-with-tune.patch
