Wilco Dijkstra writes:
> Hi Kyrill & Richard,
>
>> I was leaving this to others in case it was obvious to them. On the
>> basis that silence suggests it wasn't, :-) could you go into more details?
>> Is it expected on first principles that jump alignment doesn't matter
>> for Neoverse N1, or is t
Hi Kyrill & Richard,
> I was leaving this to others in case it was obvious to them. On the
> basis that silence suggests it wasn't, :-) could you go into more details?
> Is it expected on first principles that jump alignment doesn't matter
> for Neoverse N1, or is this purely based on experimenta
Hi Richard, Wilco,
On 1/17/20 8:43 AM, Richard Sandiford wrote:
Wilco Dijkstra writes:
> Testing shows the setting of 32:16 for jump alignment has a
significant codesize
> cost, however it doesn't make a difference in performance. So set
jump-align
> to 4 to get 1.6% codesize improvement.
I
Wilco Dijkstra writes:
> Testing shows the setting of 32:16 for jump alignment has a significant
> codesize
> cost, however it doesn't make a difference in performance. So set jump-align
> to 4 to get 1.6% codesize improvement.
I was leaving this to others in case it was obvious to them. On the
ping
Testing shows the setting of 32:16 for jump alignment has a significant codesize
cost, however it doesn't make a difference in performance. So set jump-align
to 4 to get 1.6% codesize improvement.
OK for commit?
ChangeLog
2019-12-24 Wilco Dijkstra
* config/aarch64/aarch64.c (ne
Testing shows the setting of 32:16 for jump alignment has a significant codesize
cost, however it doesn't make a difference in performance. So set jump-align
to 4 to get 1.6% codesize improvement.
OK for commit?
ChangeLog
2019-12-24 Wilco Dijkstra
* config/aarch64/aarch64.c (neoverse
