diff options
| author | Dennis Zhang <dennis.zhang@arm.com> | 2019-07-03 19:52:04 +0000 |
|---|---|---|
| committer | Richard Sandiford <rsandifo@gcc.gnu.org> | 2019-07-03 19:52:04 +0000 |
| commit | 1bbffb87a9ecc3e27a4074145e55e3315df57b7d (patch) | |
| tree | 2e3992be667b85cec674ef4bcb9bc7e31f32034e /gcc/explow.c | |
| parent | 03eddfb3b57152121154cf64fcd5c145000ee7f3 (diff) | |
| download | gcc-1bbffb87a9ecc3e27a4074145e55e3315df57b7d.zip gcc-1bbffb87a9ecc3e27a4074145e55e3315df57b7d.tar.gz gcc-1bbffb87a9ecc3e27a4074145e55e3315df57b7d.tar.bz2 | |
[AArch64] Remove constraint strings from define_expand constructs
A number of AArch64 define_expand patterns have specified constraints
for their operands. But the constraint strings are ignored at expand
time and are therefore redundant/useless. We now avoid specifying
constraints in new define_expands, but we should clean up the existing
define_expand definitions.
For example, the constraint "=w" is removed in the following case:
(define_expand "sqrt<mode>2"
[(set (match_operand:GPF_F16 0 "register_operand" "=w")
The "" marks with an empty constraint in define_expand are removed as well.
2019-07-03 Dennis Zhang <dennis.zhang@arm.com>
gcc/
* config/aarch64/aarch64.md: Remove redundant constraints from
define_expand but keep some patterns untouched if they are
specially selected by TARGET_SECONDARY_RELOAD hook.
* config/aarch64/aarch64-sve.md: Likewise.
* config/aarch64/atomics.md: Remove redundant constraints from
define_expand.
* config/aarch64/aarch64-simd.md: Likewise.
From-SVN: r273021
Diffstat (limited to 'gcc/explow.c')
0 files changed, 0 insertions, 0 deletions