Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(218)

Issue 6302064: Make timevar phases mutually exclusive.

Can't Edit
Can't Publish+Mail
Start Review
Created:
11 years, 10 months ago by Lawrence Crowl
Modified:
11 years, 10 months ago
Reviewers:
Diego Novillo, joseph, jason
CC:
gcc-patches_gcc.gnu.org
Base URL:
svn+ssh://gcc.gnu.org/svn/gcc/trunk/
Visibility:
Public.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+90 lines, -22 lines) Patch
M gcc/c-decl.c View 1 chunk +2 lines, -2 lines 0 comments Download
M gcc/cp/decl2.c View 1 chunk +2 lines, -2 lines 0 comments Download
M gcc/langhooks.c View 1 chunk +4 lines, -4 lines 0 comments Download
M gcc/lto/lto.c View 4 chunks +19 lines, -5 lines 0 comments Download
M gcc/timevar.c View 2 chunks +53 lines, -0 lines 0 comments Download
M gcc/timevar.def View 1 chunk +6 lines, -2 lines 0 comments Download
M gcc/toplev.c View 2 chunks +4 lines, -7 lines 0 comments Download

Messages

Total messages: 6
Lawrence Crowl
The intent of the phases was to have a high-level but mutually exclusive accounting of ...
11 years, 10 months ago (2012-06-11 18:45:58 UTC) #1
Diego Novillo
On 12-06-11 14:45 , Lawrence Crowl wrote: > The intent of the phases was to ...
11 years, 10 months ago (2012-06-13 12:46:45 UTC) #2
Diego Novillo
On 12-06-13 08:46 , Diego Novillo wrote: > The LTO bits are fine. I would ...
11 years, 10 months ago (2012-06-13 13:58:14 UTC) #3
joseph_codesourcery.com
On Wed, 13 Jun 2012, Diego Novillo wrote: > The LTO bits are fine. I ...
11 years, 10 months ago (2012-06-13 17:56:21 UTC) #4
jason_redhat.com
OK. Jason
11 years, 10 months ago (2012-06-14 06:00:07 UTC) #5
Lawrence Crowl
11 years, 10 months ago (2012-06-19 01:33:26 UTC) #6
On 6/13/12, Diego Novillo <dnovillo@google.com> wrote:
> On 12-06-13 08:46 , Diego Novillo wrote:
> > The LTO bits are fine. I would prefer if an FE maintainer takes
> > a second look over the other bits. Jason, Joseph?
>
> Incidentally, could you please test it with an LTO-enabled bootstrap?
>
> $ ../src/configure --with-build-config=bootstrap-lto
> --enable-languages=c++,fortran
> $ make profiledbootstrap
>
> If you cut and paste one of the -flto compiles you see during
> bootstrap, you can add -ftime-report to it to make sure that the
> LTO timers are properly setup.

I had to make a slight adjustment here.  LTO runs as a front-end,
and the parse timers are automatically started for the front ends.
But LTO is not parsing.  Rather than change every front end to
handle those timers, I turned the timers off and then back on again
within LTO.

Committed.

-- 
Lawrence Crowl
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b