.pin...@cavium.com;
> jim.wil...@linaro.org
> Cc: nd
> Subject: [PATCH][AArch64] Enable AES fusion with -mcpu=generic
>
> Many supported cores implement fusion of AES instructions. When fusion
> happens it can give a significant performance gain. If not, scheduling
> f
ping
From: Wilco Dijkstra
Sent: 16 March 2017 17:22
To: GCC Patches; Evandro Menezes; andrew.pin...@cavium.com;
jim.wil...@linaro.org
Cc: nd
Subject: [PATCH][AArch64] Enable AES fusion with -mcpu=generic
Many supported cores implement fusion of AES instructions. When fusion
happens it can
On Thu, Mar 16, 2017 at 08:26:42PM -0700, Jim Wilson wrote:
> On Thu, Mar 16, 2017 at 11:01 AM, Andrew Pinski wrote:
> > On Thu, Mar 16, 2017 at 10:22 AM, Wilco Dijkstra
> > wrote:
> >> Many supported cores implement fusion of AES instructions. When fusion
> >> happens it can give a significant
On Thu, Mar 16, 2017 at 11:01 AM, Andrew Pinski wrote:
> On Thu, Mar 16, 2017 at 10:22 AM, Wilco Dijkstra
> wrote:
>> Many supported cores implement fusion of AES instructions. When fusion
>> happens it can give a significant performance gain. If not, scheduling
>> fusion candidates next to ea
On Thu, Mar 16, 2017 at 10:22 AM, Wilco Dijkstra wrote:
> Many supported cores implement fusion of AES instructions. When fusion
> happens it can give a significant performance gain. If not, scheduling
> fusion candidates next to each other has almost no effect on performance.
> Due to the high
Many supported cores implement fusion of AES instructions. When fusion
happens it can give a significant performance gain. If not, scheduling
fusion candidates next to each other has almost no effect on performance.
Due to the high benefit/low cost it makes sense to enable AES fusion with
-mcpu=g