aboutsummaryrefslogtreecommitdiff
path: root/gcc/cp/tree.cc
diff options
context:
space:
mode:
authorRichard Sandiford <richard.sandiford@arm.com>2022-09-29 11:32:53 +0100
committerRichard Sandiford <richard.sandiford@arm.com>2022-09-29 11:32:53 +0100
commit0f244d848cffeda68f0eb4c5bb9c7e629bf2e957 (patch)
tree7fdaa27069d5d7611c60be1e9d3f3ca1393df69f /gcc/cp/tree.cc
parent198bb6ed327c74eb2b0450bf978e4e6a64a6406c (diff)
downloadgcc-0f244d848cffeda68f0eb4c5bb9c7e629bf2e957.zip
gcc-0f244d848cffeda68f0eb4c5bb9c7e629bf2e957.tar.gz
gcc-0f244d848cffeda68f0eb4c5bb9c7e629bf2e957.tar.bz2
aarch64: Remove AARCH64_FL_RCPC8_4 [PR107025]
AARCH64_FL_RCPC8_4 is an odd-one-out in that it has no associated entry in aarch64-option-extensions.def. This means that, although it is internally separated from AARCH64_FL_V8_4A, there is no mechanism for turning it on and off individually, independently of armv8.4-a. The only place that the flag was used independently was in the entry for thunderx3t110, which enabled it alongside V8_3A. As noted in PR107025, this means that any use of the extension will fail to assemble. In the PR trail, Andrew suggested removing the core entry. That might be best long-term, but since the barrier for removing command-line options without a deprecation period is very high, this patch instead just drops the flag from the core entry. We'll still produce correct code. gcc/ PR target/107025 * config/aarch64/aarch64.h (oAARCH64_FL_RCPC8_4): Delete. (AARCH64_FL_FOR_V8_4A): Update accordingly. (AARCH64_ISA_RCPC8_4): Use AARCH64_FL_V8_4A directly. * config/aarch64/aarch64-cores.def (thunderx3t110): Remove AARCH64_FL_RCPC8_4.
Diffstat (limited to 'gcc/cp/tree.cc')
0 files changed, 0 insertions, 0 deletions