Re: HELP: GCC Passes and Files

[Jim Wilson <wilson at specifixinc dot com>]

perugupa@csee.wvu.edu wrote:
> builtins.c

built-in function support.  Used by several language front ends, 
primarly C/C++.

> collect2.c

Linker front-end for things like C++ static constructors/destructors, 
template repositories.  Not used by all targets.  Should be considered 
part of gcc driver.

> cfgbuild.c

Builds a cfg.  Infrastructure used by a number of optimization passes.

> enquire.c

Build time only, not part of gcc binary.  Produces FP constants suitable 
for float.h header file.  No longer used, except possibly for an initial 
port.  Has since been deleted from code base.

> diagnostic.c

Prints diagnostics.  Used in multiple places.

> timevar.c

Prints timing info used for simple gcc profiling.  Part of compiler 
infrastructure.

> sbitmap.c

bitmap data structures.  Part of infrastructure.  Used in multiple places.

> intl.c

Internationalization code.  Used in multiple places, anyplace that 
parses or prints strings.

> linemap.c

Tracks file names and line numbers.  Used for printing diagnostics in 
the preprocessor.

> mkdeps.c

Makefile dependency generator.  Used in preprocessor.

> params.c

Used for run-time controllable parameters, cf the --parm option. 
Infrastructure used in many optimization passes.

> prefix.c

Used for converting file name paths, intended for Windows registry 
support, but not really used by anyone.  Infrastructure.

> hash.c
> hastab.c
> hashtable.c

hash table data structures.  Infrastructure used in multiple places.

> ggc-common.c
> ggc-none.c
> ggc-page.c

gcc garbage collector for memory management.  Infrastructure, used in 
multiple places.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com