On 11/05/18 14:29, Kyrill Tkachov wrote:
> Hi all,
>
> 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 macr
Hi all,
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
