This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: where the compilation process stops in gcc
- From: "Dave Korn" <dk at artimi dot com>
- To: <perugupa at csee dot wvu dot edu>,<wilson at specifixinc dot com>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Mon, 28 Jun 2004 12:13:18 +0100
- Subject: RE: where the compilation process stops in gcc
> -----Original Message-----
> From: gcc-owner On Behalf Of perugupa
> Sent: 26 June 2004 19:46
> > Yes, the compiler starts and ends in toplev.c, though some language
> > front ends may add extra stuff around toplev.c. See toplev_main,
> > do_compile, compile_file, etc.
>
> Hi,
> Thanx for the reply Jim.i found that functions in toplev.c
> are 'being
> called' by the functions in other passes less frequently
> compared to the
> calls 'made by' the functions in this file.
> is there any specific function or a point in toplev.c,
> where the process
> ends.
You could say that the call from do_compile () to finalize () in toplev.c
marks the end of compilation, since that's when all the output files are
closed.
cheers,
DaveK
--
Can't think of a witty .sigline today....