Displaying 4 results from an estimated 4 matches for "r259673".
Did you mean:
259673
2016 Mar 31
0
RFC: Large, especially super-linear, compile time regressions are bugs.
...ow the same policy for compile
time regressions that are large, and especially for ones that are
super-linear. As an example from the previous thread:
On Mon, Mar 14, 2016 at 12:14 PM Bruno Cardoso Lopes via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> > There is a possibility that r259673 could play a role here.
> >
> > For the buildSchedGraph() method, there is the -dag-maps-huge-region that
> > has the default value of 1000. When I commited the patch, I was expecting
> > people to lower this value as needed and also suggested this, but this
> has
> &g...
2016 Mar 14
4
llvm and clang are getting slower
Hi,
> There is a possibility that r259673 could play a role here.
>
> For the buildSchedGraph() method, there is the -dag-maps-huge-region that
> has the default value of 1000. When I commited the patch, I was expecting
> people to lower this value as needed and also suggested this, but this has
> not happened. 1000 is very...
2016 Mar 31
3
RFC: Large, especially super-linear, compile time regressions are bugs.
...at are large, and especially for ones that are super-linear. As an example from the previous thread:
>
> On Mon, Mar 14, 2016 at 12:14 PM Bruno Cardoso Lopes via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> > There is a possibility that r259673 could play a role here.
> >
> > For the buildSchedGraph() method, there is the -dag-maps-huge-region that
> > has the default value of 1000. When I commited the patch, I was expecting
> > people to lower this value as needed and also suggested this, but this has
> > no...
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