search for: mem_byt

...arger. This was about 2.8% before the Localizer pass landed, so a slight regression. >> >> That one is surprising. Do you have an idea of what is happening? >> Alternatively if you can point me to the biggest offender, I can have a look. > > So the biggest offenders on the mem_bytes metric in LNT are: > O0 -g O0 -g gisel-with-localizer O0 -g gisel-without-localizer > SingleSource/Benchmarks/Misc/perlin 14272 14640 18344 25.95% > SingleSource/Benchmarks/Dhrystone/dry 16560 17144 20160 18.21% > SingleSource/Benchmarks/Stanford/QueensProfile 13912 14192 15136 6.79%...

...This was about 2.8% before the Localizer pass > landed, so a slight regression. > > > That one is surprising. Do you have an idea of what is happening? > Alternatively if you can point me to the biggest offender, I can have a > look. > > > So the biggest offenders on the mem_bytes metric in LNT are: > O0 -g O0 -g gisel-with-localizer O0 -g gisel-without-localizer > SingleSource/Benchmarks/Misc/perlin 14272 14640 18344 25.95% > SingleSource/Benchmarks/Dhrystone/dry 16560 17144 20160 18.21% > SingleSource/Benchmarks/Stanford/QueensProfile 13912 14192 15136 6.79%...

...lizer pass >> landed, so a slight regression. >> >> >> That one is surprising. Do you have an idea of what is happening? >> Alternatively if you can point me to the biggest offender, I can have a >> look. >> >> >> So the biggest offenders on the mem_bytes metric in LNT are: >> O0 -g O0 -g gisel-with-localizer O0 -g gisel-without-localizer >> SingleSource/Benchmarks/Misc/perlin 14272 14640 18344 25.95% >> SingleSource/Benchmarks/Dhrystone/dry 16560 17144 20160 18.21% >> SingleSource/Benchmarks/Stanford/QueensProfile 13912 14...

Hi Kristof, Thanks for the updated numbers. > On May 31, 2017, at 7:45 AM, Kristof Beyls <kristof.beyls at arm.com> wrote: > >> >> On 31 May 2017, at 15:33, Diana Picus via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> Cool test :) >> It seems to work fine now, I don't see any new failures.