On Wed, 10 Aug 2016, Richard Biener wrote:
> On Wed, 10 Aug 2016, David Malcolm wrote:
>
> > On Wed, 2016-08-10 at 14:04 +0200, Richard Biener wrote:
> > > The following patch adds the ability to record time spent in utility
> > > to the pass using it. For things like CFG cleanup, alias stmt
> >
On Wed, 10 Aug 2016, David Malcolm wrote:
> Looks like inside a pop there's a lazy allocation of a map, and a
> get_or_insert. Could this make -ftime-report have an impact on the
> timing?
-ftime-report already has a great impact on timing because it adds a syscall on
each timevar change (which h
On Wed, 10 Aug 2016, David Malcolm wrote:
> On Wed, 2016-08-10 at 14:04 +0200, Richard Biener wrote:
> > The following patch adds the ability to record time spent in utility
> > to the pass using it. For things like CFG cleanup, alias stmt
> > walking
> > or DF infrastructure work it is currently
> Index: gcc/doc/invoke.texi
> ===
> --- gcc/doc/invoke.texi (revision 238469)
> +++ gcc/doc/invoke.texi (working copy)
[snip]
> @@ -12543,6 +12543,10 @@ print some statistics about each pass wh
> Makes the compiler print
On Wed, 2016-08-10 at 14:04 +0200, Richard Biener wrote:
> The following patch adds the ability to record time spent in utility
> to the pass using it. For things like CFG cleanup, alias stmt
> walking
> or DF infrastructure work it is currently not visible which pass is
> responsible for the time
The following patch adds the ability to record time spent in utility
to the pass using it. For things like CFG cleanup, alias stmt walking
or DF infrastructure work it is currently not visible which pass is
responsible for the time spent there. With -ftime-report-details
you now get
alias stmt