aboutsummaryrefslogtreecommitdiff
path: root/liboffloadmic
diff options
context:
space:
mode:
authorKyrylo Tkachov <kyrylo.tkachov@arm.com>2018-05-14 16:29:13 +0000
committerKyrylo Tkachov <ktkachov@gcc.gnu.org>2018-05-14 16:29:13 +0000
commit10c54e5b0e098b5b1e7a0b79716bc113fe96c45e (patch)
treeeca5aa957a2478f1838484727fc83df4398d9efb /liboffloadmic
parent43d0a8ee88460a1161264c0c1a68e063493c3f20 (diff)
downloadgcc-10c54e5b0e098b5b1e7a0b79716bc113fe96c45e.zip
gcc-10c54e5b0e098b5b1e7a0b79716bc113fe96c45e.tar.gz
gcc-10c54e5b0e098b5b1e7a0b79716bc113fe96c45e.tar.bz2
[AArch64] Add combine pattern to fuse AESE/AESMC instructions
When the AESE,AESD and AESMC, AESMC instructions are generated through the appropriate arm_neon.h intrinsics we really want to keep them together when the AESE feeds into an AESMC and fusion is supported by the target CPU. We have macro-fusion hooks and scheduling model forwarding paths defined to facilitate that. It is, however, not always enough. This patch adds another mechanism for doing that. When we can detect during combine that the required dependency is exists (AESE -> AESMC, AESD -> AESIMC) just keep them together with a combine pattern throughout the rest of compilation. We won't ever want to split them. The testcases generate 4 AESE(D) instructions in a block followed by 4 AES(I)MC instructions that consume the corresponding results and it also adds a bunch of computations in-between so that the AESE and AESMC instructions are not trivially back-to-back, thus exercising the compiler's ability to bring them together. With this patch all 4 pairs are fused whereas before a couple of fusions would be missed due to intervening arithmetic and memory instructions. * config/aarch64/aarch64-simd.md (*aarch64_crypto_aese_fused): New pattern. (aarch64_crypto_aesd_fused): Likewise. * gcc.target/aarch64/crypto-fuse-1.c: New test. * gcc.target/aarch64/crypto-fuse-2.c: Likewise. From-SVN: r260234
Diffstat (limited to 'liboffloadmic')
0 files changed, 0 insertions, 0 deletions