aboutsummaryrefslogtreecommitdiff
path: root/gcc/common/config/aarch64
diff options
context:
space:
mode:
authorTamar Christina <tamar.christina@arm.com>2020-04-03 15:18:35 +0100
committerTamar Christina <tamar.christina@arm.com>2020-04-03 15:19:33 +0100
commit53161358180fdc2c2c21c8f46bbdd339a1fbb8ae (patch)
tree1e09e8907db29053e0707bca2dc10ba38baebeaa /gcc/common/config/aarch64
parentef6631051d4bb9519f3f0dd5f3b3eadbd67bc10a (diff)
downloadgcc-53161358180fdc2c2c21c8f46bbdd339a1fbb8ae.zip
gcc-53161358180fdc2c2c21c8f46bbdd339a1fbb8ae.tar.gz
gcc-53161358180fdc2c2c21c8f46bbdd339a1fbb8ae.tar.bz2
AArch64: Fix options canonicalization for assembler
It is currently impossible to use fp16 on any architecture higher than Armv8.3-a due to a bug in options canonization. This bug results in the fp16 flag not being emitted in the assembly when it should have been. This is caused by a complicated architectural requirement at Armv8.4-a. On Armv8.2-a and Armv8.3-a fp16fml is an optional extension and turning it on turns on both fp and fp16. However starting with Armv8.4-a fp16fml is mandatory if fp16 is available, otherwise it's optional. In short this means that to enable fp16fml the smallest option that needs to passed to the assembler is Armv8.4-a+fp16. The fix in this patch takes into account that an option may be on by default in an architecture, but that not all the bits required to use it are on by default in an architecture. In such cases the difference between the two are still emitted to the assembler. gcc/ChangeLog: PR target/94396 * common/config/aarch64/aarch64-common.c (aarch64_get_extension_string_for_isa_flags): Handle default flags. gcc/testsuite/ChangeLog: PR target/94396 * gcc.target/aarch64/options_set_11.c: New test. * gcc.target/aarch64/options_set_12.c: New test. * gcc.target/aarch64/options_set_13.c: New test. * gcc.target/aarch64/options_set_14.c: New test. * gcc.target/aarch64/options_set_15.c: New test. * gcc.target/aarch64/options_set_16.c: New test. * gcc.target/aarch64/options_set_17.c: New test. * gcc.target/aarch64/options_set_18.c: New test. * gcc.target/aarch64/options_set_19.c: New test. * gcc.target/aarch64/options_set_20.c: New test. * gcc.target/aarch64/options_set_21.c: New test. * gcc.target/aarch64/options_set_22.c: New test. * gcc.target/aarch64/options_set_23.c: New test. * gcc.target/aarch64/options_set_24.c: New test. * gcc.target/aarch64/options_set_25.c: New test. * gcc.target/aarch64/options_set_26.c: New test.
Diffstat (limited to 'gcc/common/config/aarch64')
-rw-r--r--gcc/common/config/aarch64/aarch64-common.c17
1 files changed, 16 insertions, 1 deletions
diff --git a/gcc/common/config/aarch64/aarch64-common.c b/gcc/common/config/aarch64/aarch64-common.c
index 8d24c14..0bddcc8 100644
--- a/gcc/common/config/aarch64/aarch64-common.c
+++ b/gcc/common/config/aarch64/aarch64-common.c
@@ -391,7 +391,22 @@ aarch64_get_extension_string_for_isa_flags (uint64_t isa_flags,
/* We remove all the dependent bits, to prevent them from being turned
on twice. This only works because we assume that all there are
individual options to set all bits standalone. */
- isa_flag_bits &= ~opt->flags_on;
+
+ /* PR target/94396.
+
+ For flags which would already imply a bit that's on by default (e.g
+ fp16fml which implies +fp,+fp16) we must emit the flags that are not
+ on by default. i.e. in Armv8.4-a +fp16fml is default if +fp16. So
+ if a user passes armv8.4-a+fp16 (or +fp16fml) then we need to emit
+ +fp16. But if +fp16fml is used in an architecture where it is
+ completely optional we only have to emit the canonical flag. */
+ uint64_t toggle_bits = opt->flags_on & default_arch_flags;
+ /* Now check to see if the canonical flag is on by default. If it
+ is not then enabling it will enable all bits in flags_on. */
+ if ((opt->flag_canonical & default_arch_flags) == 0)
+ toggle_bits = opt->flags_on;
+
+ isa_flag_bits &= ~toggle_bits;
isa_flag_bits |= opt->flag_canonical;
}
}