aboutsummaryrefslogtreecommitdiff
path: root/gcc/config.gcc
diff options
context:
space:
mode:
authorRichard Sandiford <richard.sandiford@arm.com>2024-11-11 12:32:14 +0000
committerRichard Sandiford <richard.sandiford@arm.com>2024-11-11 12:32:14 +0000
commit22d25b1fee6656df3203dc8ffee6d1d55fc1a7fd (patch)
tree597373bdfd14982a968b16f2718ddae5d0913fb3 /gcc/config.gcc
parent0c9a5ed01662daca5f30b3861db8680b377feb71 (diff)
downloadgcc-22d25b1fee6656df3203dc8ffee6d1d55fc1a7fd.zip
gcc-22d25b1fee6656df3203dc8ffee6d1d55fc1a7fd.tar.gz
gcc-22d25b1fee6656df3203dc8ffee6d1d55fc1a7fd.tar.bz2
aarch64: Test TARGET_STREAMING instead of TARGET_STREAMING_SME
g:ede97598e2c recorded separate ISA requirements for streaming and non-streaming mode. The premise there was that AARCH64_FL_SME should not be included in the streaming mode requirements, since: (a) an __arm_streaming_compatible function wouldn't be in streaming mode if SME wasn't available. (b) __arm_streaming_compatible functions only allow things that are possible in non-streaming mode, so the non-streaming architecture is enough to assemble the code, even if +sme isn't enabled. (c) we reject __arm_streaming if +sme isn't enabled, so don't need to test it for individual intrinsics as well. Later patches lean into this further. This patch applies the same reasoning to the .md constructs for base streaming-only SME instructions, guarding them with TARGET_STREAMING rather than TARGET_STREAMING_SME. gcc/ * config/aarch64/aarch64.h (TARGET_SME): Expand comment. (TARGET_STREAMING_SME): Delete. * config/aarch64/aarch64-sme.md: Use TARGET_STREAMING instead of TARGET_STREAMING_SME. * config/aarch64/aarch64-sve2.md: Likewise.
Diffstat (limited to 'gcc/config.gcc')
0 files changed, 0 insertions, 0 deletions