Displaying 3 results from an estimated 3 matches for "backendratio".
2016 Mar 08
4
llvm and clang are getting slower
...Ratio = 1.29385
For simplicity, let's use a simple linear model for the distribution of
slowdown between the frontend and backend: a constant factor slowdown for
the backend, and an independent constant factor slowdown for the frontend.
This gives the following linear system:
debugRatio = .1 * backendRatio + (1 - .1) * frontendRatio
releaseRatio = .33 * backendRatio + (1 - .33) * frontendRatio
Solving this linear system we find that under this simple model, the
expected slowdown factors are:
backendRatio = 1.77783
frontendRatio = 1.05547
Intuitively, backendRatio comes out larger in this comparison...
2016 Mar 09
2
llvm and clang are getting slower
...simplicity, let's use a simple linear model for the distribution of
> slowdown between the frontend and backend: a constant factor slowdown for
> the backend, and an independent constant factor slowdown for the frontend.
> This gives the following linear system:
> debugRatio = .1 * backendRatio + (1 - .1) * frontendRatio
> releaseRatio = .33 * backendRatio + (1 - .33) * frontendRatio
>
> Solving this linear system we find that under this simple model, the
> expected slowdown factors are:
> backendRatio = 1.77783
> frontendRatio = 1.05547
>
> Intuitively, backendRat...
2016 Mar 08
9
llvm and clang are getting slower
I have just benchmarked building trunk llvm and clang in Debug,
Release and LTO modes (see the attached scrip for the cmake lines).
The compilers used were clang 3.5, 3.6, 3.7, 3.8 and trunk. In all
cases I used the system libgcc and libstdc++.
For release builds there is a monotonic increase in each version. From
163 minutes with 3.5 to 212 minutes with trunk. For comparison, gcc
5.3.2 takes