From Wikipedia, the free encyclopedia

GNU Compiler Collection
Developer:	GNU Project
Latest release:	4.2.2 / 7 October 2007
OS:	Cross-platform
Platform:	GNU
Genre:	Compiler
License:	GNU General Public License, GNU Lesser General Public License
Website:	http://gcc.gnu.org/

The GNU Compiler Collection (usually shortened to GCC) is a set of compilers produced for various programming languages by the GNU Project. GCC is a key component of the GNU toolchain. As well as being the official compiler of the GNU system, GCC has been adopted as the standard compiler by most other modern Unix-like computer operating systems, including Linux, the BSD family and Mac OS X. GCC has been ported to a wide variety of computer architectures, and is widely deployed as a tool in commercial and closed development environments. GCC is also used in popular embedded platforms like Symbian^[1], Playstation and Sega Dreamcast.^{[citation needed]}

Originally named the GNU C Compiler, because it only handled the C programming language, GCC 1.0 was released in 1987, and the compiler was extended to compile C++ in December of that year.^[2] Front ends were later developed for Fortran, Pascal, Objective C, Java, and Ada, among others.^[3]

Distributed by the Free Software Foundation (FSF) under the terms of the GNU General Public License (GNU GPL) and the GNU Lesser General Public License (GNU LGPL), GCC is free software.

Contents 1 History 2 Languages 3 Architectures 4 Structure 4.1 Front ends 4.2 Optimization 4.3 Back end 5 Debugging GCC programs 6 See also 7 References 8 Further reading 9 External links

[edit] History

GCC was started by Richard Stallman in 1985. He extended an existing compiler to compile C. The compiler originally compiled Pastel, an extended, nonportable dialect of Pascal, and was written in Pastel. It was rewritten in C by Len Tower and Stallman,^[4] and released in 1987^[5] as the compiler for the GNU Project, in order to have a compiler available that was free software. Its development was supervised by the Free Software Foundation.^[6]

In 1997, a group of developers, dissatisfied with the slow pace and closed nature of official GCC development, formed a project called EGCS (Experimental/Enhanced GNU Compiler System), which merged several experimental forks into a single project forked from GCC. EGCS development subsequently proved more vigorous than GCC development, and EGCS was eventually "blessed" as the official version of GCC in April 1999.

GCC is now maintained by a varied group of programmers from around the world. It has been ported to more kinds of processors and operating systems than any other compiler.^[7]

GCC is often the compiler of choice for developing software that is required to execute on a wide variety of hardware. Differences in native compilers lead to difficulties in developing code that will compile correctly on all the compilers and build scripts that will run for all the platforms. By using GCC, the same parser is used for all platforms, so if the code compiles on one, chances are high that it compiles on all.

[edit] Languages

The standard compiler release 4.2 includes front ends for: C, C++ (G++), Java (GCJ), Ada (GNAT), Objective-C, Objective-C++, and Fortran (GFortran). Also available, but not in standard are: Modula-2, Modula-3, Pascal, PL/I, D, Mercury, VHDL.

The Fortran front end was g77 before version 4.0, which only supports Fortran 77. In newer versions, g77 was dropped in favor of the new GFortran front end that supports Fortran 95. A front end for CHILL was previously included, but has been dropped owing to a lack of maintenance.

[edit] Architectures

GCC target processors as of version 4.1 include:

Lesser-known target processors supported in the standard release have included:

Additional processors have been supported by GCC versions maintained separately from the FSF version:

When retargeting GCC to a new platform, bootstrapping is often used.

[edit] Structure

GCC's external interface is generally standard for a Unix compiler. Users invoke a driver program named gcc, which interprets command arguments, decides which language compilers to use for each input file, runs the assembler on their output, and then possibly runs the linker to produce a complete executable binary.

Each of the language compilers is a separate program that takes in source code and produces assembly language. All have a common internal structure. A per-language front end parses the source code in that language and produces an abstract syntax tree ("tree" for short), and a back end converts the trees to GCC's Register Transfer Language (RTL). Compiler optimizations and static code analysis techniques (such as FORTIFY_SOURCE[2], a compiler directive which attempts to discover some buffer overflows) are applied to the code. Finally, assembly language is produced using architecture-specific pattern matching originally based on an algorithm of Jack Davidson and Chris Fraser.

Nearly all of GCC is written in C with the exception of the Ada frontend; much of the Ada frontend is written in Ada.

[edit] Front ends

Frontends vary internally, having to produce trees that can be handled by the backend. The parsers are hand-coded recursive descent parsers.

Until recently, the tree representation of the program was not fully independent of the processor being targeted. Confusingly, the meaning of a tree was somewhat different for different language front-ends, and front-ends could provide their own tree codes.

In 2005, two new forms of language-independent trees were introduced. These new tree formats are called GENERIC and GIMPLE. Parsing is now done by creating temporary language-dependent trees, and converting them to GENERIC. The so-called "gimplifier" then lowers this more complex form into the simpler SSA-based GIMPLE form which is the common language for a large number of new powerful language- and architecture-independent global (function scope) optimizations.

[edit] Optimization

Optimization on trees does not generally fit into what most compiler developers would consider a front end task, as it is not language dependent and does not involve parsing. GCC developers have given this part of the compiler the somewhat contradictory name the "middle end." These optimizations include dead code elimination, partial redundancy elimination, global value numbering, sparse conditional constant propagation, and scalar replacement of aggregates. Array dependence based optimizations such as automatic vectorization are currently being developed.

[edit] Back end

The behavior of the GCC back end is partly specified by preprocessor macros and functions specific to a target architecture, for instance to define the endianness, word size, and calling conventions. The front part of the back end uses these to help decide RTL generation, so although GCC's RTL is nominally processor-independent, the initial sequence of abstract instructions is already adapted to the target.

The exact set of GCC optimizations varies from release to release as it develops, but includes the standard algorithms, such as loop optimization, jump threading, common subexpression elimination, instruction scheduling, and so forth. The RTL optimizations are of less importance with the recent addition of global SSA-based optimizations on GIMPLE trees[3], as RTL optimizations have a much more limited scope, and have less high-level information.

A "reloading" phase changes abstract (pseudo-) registers into real machine registers, using data collected from the patterns describing the target's instruction set. This is a somewhat complicated phase, because it must account for the vagaries of all of GCC's targets.

The final phase is somewhat anticlimactic, since the patterns to match were generally chosen during reloading, and so the assembly code is simply built by running substitutions of registers and addresses into the strings specifying the instructions.

[edit] Debugging GCC programs

The primary tool for debugging GCC code is the GNU Debugger (gdb). Among more specialized tools are Valgrind for finding memory errors and leaks. The GNU Profiler (gprof) can be used to find out how much time is spent in which routines, and how often they are called; this requires compiling programs with special profiling options.

[edit] See also

• distcc
• introspector (program)
• LLVM
• MinGW
• OpenMP
• DJGPP
• GCC Summit
• OpenWatcom
• Boehm GC

[edit] References

[edit] Further reading

[edit] External links

• GCC homepage
• GCC Forum
• Kerner, Sean Michael. "Open Source GCC 4.0: Older, Faster", internetnews.com, April 22, 2005. 
• Kerner, Sean Michael. "New GCC Heavy on Optimization", internetnews.com, March 2, 2006. 
• Marketing Cygnus Support, an essay covering GCC development for the 1990s, with 30 monthly reports for in the "Inside Cygnus Engineering" section near the end.

v • d • e GNU Project
History	GNU Manifesto · GNU Project · Free Software Foundation · History of free software
GNU licenses	GNU General Public License · GNU Lesser General Public License · GNU Free Documentation License · GPL linking exception
Software	GNU (Variants) · GNOME · Gnuzilla · Gnash · Bash · GCC · GNU Emacs · glibc · Coreutils · GNU build system · Other GNU packages and programs
Speakers	Robert J. Chassell · Loïc Dachary · Ricardo Galli · Georg C. F. Greve · Federico Heinz · Benjamin Mako Hill · Bradley M. Kuhn · Eben Moglen · Brett Smith  · Richard Stallman · John Sullivan