aboutsummaryrefslogtreecommitdiff
path: root/gcc/fortran/trans-array.c
diff options
context:
space:
mode:
authorRichard Sandiford <richard.sandiford@arm.com>2019-07-06 08:26:44 +0000
committerRichard Sandiford <rsandifo@gcc.gnu.org>2019-07-06 08:26:44 +0000
commitef2df51671bb6c755302ffe8e36eae0755882ad2 (patch)
tree93c55ae89a44df72b1ba94d42e33819a12a0ba1d /gcc/fortran/trans-array.c
parenta0cb70b7ea2b522f02a2384fbe1103d69904f916 (diff)
downloadgcc-ef2df51671bb6c755302ffe8e36eae0755882ad2.zip
gcc-ef2df51671bb6c755302ffe8e36eae0755882ad2.tar.gz
gcc-ef2df51671bb6c755302ffe8e36eae0755882ad2.tar.bz2
[s390] Fix ambiguous .md attribute uses
This patch is part of a series that fixes ambiguous attribute uses in .md files, i.e. cases in which attributes didn't use <ITER:ATTR> to specify an iterator, and in which <ATTR> could have different values depending on the iterator chosen. The vx-builtins.md part changes the choice of <mode> from the implicit <VFCMP:mode> to an explicit <VF_HW:mode> (i.e. from the mode of the comparison result to the mode of the operands being compared). That seemed like the intended behaviour given later patterns like vec_cmpeq<mode>_cc. The use of BFP in the s390.md LNDFR pattern looks like a typo, since the operand to (abs ...) has to have the same mode as the result. The only effect before this series was to create some extra variants that would never match, making it harmless apart from very minor code bloat. 2019-07-06 Richard Sandiford <richard.sandiford@arm.com> gcc/ * config/s390/s390.md (*negabs<FP:mode>2_nocc): Use FP for operand 1. * config/s390/vx-builtins.md (*vec_cmp<insn_cmp><mode>_cconly): Make the choice of <mode> explicit, giving... (*vec_cmp<insn_cmp><VF_HW:mode>_cconly): ...this. From-SVN: r273162
Diffstat (limited to 'gcc/fortran/trans-array.c')
0 files changed, 0 insertions, 0 deletions