On 24 November 2014 at 13:46, Wilco Dijkstra <wdijk...@arm.com> wrote: >> Richard Earnshaw wrote: >> If all cores seem to benefit from FP reassociation set to 4, then it >> seems odd that 4 is not also the default for generic. >> >> Andrew, you may need to pick a target-specific value for ThunderX; I >> think Wilco has just picked something that seems plausible because he >> needs to put a real value in there. >> >> What happens if the integer and vector numbers are bumped up? I'd have >> thought that integer numbers >1 would be appropriate on all dual-issue >> or greater cores. > > I tried int and vector as well, and setting int to 2 did give an improvement, > but vector had no effect, so I'll leave to 1 for now. The patch is the same > as last time, it just sets integer to 2, and uses the same settings for all > CPUs. > > OK for commit? > > ChangeLog: > 2014-11-24 Wilco Dijkstra <wdijk...@arm.com> > > * gcc/config/aarch64/aarch64-protos.h (tune-params): > Add reasociation tuning parameters. > * gcc/config/aarch64/aarch64.c (TARGET_SCHED_REASSOCIATION_WIDTH): > Define. (aarch64_reassociation_width): New function. > (generic_tunings) Add reassociation tuning parameters. > (cortexa53_tunings): Likewise. > (cortexa57_tunings): Likewise. > (thunderx_tunings): Likewise.
OK /Marcus