This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: how does cc1plus work internally

From: Brian Dessent <brian at dessent dot net>
To: gcc-help at gcc dot gnu dot org
Date: Tue, 11 Jul 2006 19:48:44 -0700
Subject: Re: how does cc1plus work internally
References: <313c82560607111926i62e869f3nc7f9cad8add53d94@mail.gmail.com>
Reply-to: gcc-help at gcc dot gnu dot org

Yu Yang wrote:

> /usr/local/libexec/gcc/i686-pc-linux-gnu/4.1.1/cc1plus test.i.cc.
> At the end, cc1plush will print out some statistical info as the end of this
> email shows.  Beside the source code, Is there any documentation around
> that describe these stages?  The gcc internals does not talk much about this.

You don't have to run cc1plus to get this, you can supply -ftime-report
when compiling as normal.  There are many other debug dump options to
see what the compiler is doing internally -- see section 3.9 of the
manual.

The -ftime-report output tells you how much time was spent in each
pass.  Passes are documented in section 8 of the internals manual.

Brian

References:
- how does cc1plus work internally
  - From: Yu Yang

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]