Displaying 3 results from an estimated 3 matches for "release35".
Did you mean:
release_35
2016 Mar 08
4
llvm and clang are getting slower
....5 and trunk.
For debug, the user time jumps from 174m50.251s to 197m9.932s.
That's {10490.3, 11829.9} seconds, respectively.
For release, the corresponding numbers are:
{9826.71, 12714.3} seconds.
debug35 = 10490.251
debugTrunk = 11829.932
debugTrunk/debug35 == 1.12771
debugRatio = 1.12771
release35 = 9826.705
releaseTrunk = 12714.288
releaseTrunk/release35 == 1.29385
releaseRatio = 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 slowdo...
2016 Mar 09
2
llvm and clang are getting slower
...74m50.251s to 197m9.932s.
> That's {10490.3, 11829.9} seconds, respectively.
> For release, the corresponding numbers are:
> {9826.71, 12714.3} seconds.
>
> debug35 = 10490.251
> debugTrunk = 11829.932
>
> debugTrunk/debug35 == 1.12771
> debugRatio = 1.12771
>
> release35 = 9826.705
> releaseTrunk = 12714.288
>
> releaseTrunk/release35 == 1.29385
> releaseRatio = 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...
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