Richard Biener <richard.guent...@gmail.com> writes: > On Tue, Oct 24, 2017 at 1:18 PM, Richard Sandiford > <richard.sandif...@linaro.org> wrote: >> Richard Biener <richard.guent...@gmail.com> writes: >>> Do you have any numbers on the effect of poly-int on compile-times? >>> Esp. for example on stage2 build times when stage1 is -O0 -g "optimized"? >> >> I've just tried that for an x86_64 -j24 build and got: >> >> real: +7% >> user: +8.6% >> >> I don't know how noisy the results are though. > > What's the same on AARCH64 where NUM_POLY_INT_COEFFS is 2? > >> It's compile-time neutral in terms of running a gcc built with >> --enable-checking=release, within a margin of about [-0.1%, 0.1%]. > > I would have expected that (on x86_64). Well, hoped (you basically > stated that in 000/nnn.
Sorry, wasn't sure how much of the series you'd had a chance to read. > The question is what is the effect on AARCH64. > As you know we build openSUSE for AARCH64 and build power is limited ;) The timings for an AArch64 stage2-bubble with an -O0 -g stage1, for NUM_POLY_INT_COEFFS==2 is: real: +17% user: +20% Running a gcc built with --enable-checking=release is ~1% slower when using -g and ~2% slower with -O2 -g. Thanks, Richard
