Open Access Articles- Top Results for GNU Compiler Collection

GNU Compiler Collection

"Cc1" redirects here. For other uses, see CC1 (disambiguation).
GNU Compiler Collection
Developer(s) GNU Project
Initial release May 23, 1987; 33 years ago (1987-05-23)[1]
Stable release 5.1[2] / April 22, 2015; 5 years ago (2015-04-22)
Written in C++;[3] originally C
Operating system Cross-platform
Platform GNU
Type Compiler
License GNU GPL 3+ with GCC Runtime Library Exception[4]

The GNU Compiler Collection (GCC) is a compiler system produced by the GNU Project supporting various programming languages. GCC is a key component of the GNU toolchain. The Free Software Foundation (FSF) distributes GCC under the GNU General Public License (GNU GPL). GCC has played an important role in the growth of free software, as both a tool and an example.

Originally named the GNU C Compiler, when it only handled the C programming language, GCC 1.0 was released in 1987.[1] It was extended to compile C++ in December of that year. Front ends were later developed for Objective-C, Objective-C++, Fortran, Java, Ada, and Go among others.[5]

GCC has been ported to a wide variety of processor architectures, and is widely deployed as a tool in the development of both free and proprietary software. GCC is also available for most embedded platforms, including Symbian (called gcce),[6] AMCC, and Freescale Power Architecture-based chips.[7] The compiler can target a wide variety of platforms, including video game consoles such as the PlayStation 2[8] and Dreamcast.[9]

As well as being the official compiler of the GNU operating system, GCC has been adopted as the standard compiler by many other modern Unix-like computer operating systems, including Linux and the BSD family, although FreeBSD is moving to the LLVM system. Versions are also available for Microsoft Windows and other operating systems.


In an effort to bootstrap the GNU operating system, Richard Stallman asked Andrew S. Tanenbaum, the author of the Amsterdam Compiler Kit (also known as the Free University Compiler Kit) if he could use that software for GNU. When Tanenbaum told him that while the Free University was free, the compiler was not, Stallman decided to write his own.[10] Stallman's initial plan[11] was to rewrite an existing compiler from Lawrence Livermore Laboratory from Pastel to C with some help from Len Tower and others.[12] Stallman wrote a new C front end for the Livermore compiler, but then realized that it required megabytes of stack space, an impossibility on a 68000 Unix system with only 64K, and concluded he would have to write a new compiler from scratch.[11] None of the Pastel compiler code ended up in GCC, though Stallman did use the C front end he had written.[11]

GCC was first released March 22, 1987, available by FTP from MIT.[13] Stallman was listed as the author but cited others for their contributions, including Jack Davidson and Christopher Fraser for the idea of using RTL as an intermediate language, Paul Rubin for writing most of the preprocessor and Leonard Tower for "parts of the parser, RTL generator, RTL definitions, and of the Vax machine description."[14]

By 1991, GCC 1.x had reached a point of stability, but architectural limitations prevented many desired improvements, so the FSF started work on GCC 2.x.[citation needed]

As GCC was licensed under the GPL, programmers wanting to work in other directions — particularly those writing interfaces for languages other than C — were free to develop their own fork of the compiler, provided they meet the GPL's terms, including its requirements to distribute source code. Multiple forks proved inefficient and unwieldy, however, and the difficulty in getting work accepted by the official GCC project was greatly frustrating for many.[15] The FSF kept such close control on what was added to the official version of GCC 2.x that GCC was used as one example of the "cathedral" development model in Eric S. Raymond's essay The Cathedral and the Bazaar.

With the release of 4.4BSD in 1994, GCC became the default compiler for most BSD systems.[citation needed]

In 1997, a group of developers formed EGCS — Experimental/Enhanced GNU Compiler System[15][16] — to merge several experimental forks into a single project. The basis of the merger was a GCC development snapshot taken between the 2.7 and 2.81 releases. Projects merged included g77 (Fortran), PGCC (P5 Pentium-optimized GCC), many C++ improvements, and many new architectures and operating system variants.[17][18] EGCS development proved considerably more vigorous than GCC development, so much so that the FSF officially halted development on their GCC 2.x compiler, blessed EGCS as the official version of GCC and appointed the EGCS project as the GCC maintainers in April 1999. With the release of GCC 2.95 in July 1999 the two projects were once again united.

GCC has since been maintained by a varied group of programmers from around the world under the direction of a steering committee.[19] It has been ported to more kinds of processors and operating systems than any other compiler.[20][unreliable source?]


File:Linux kernel interfaces.svg
To obtain a stable ABI, like e.g. the Linux Standard Base aims to procure, the Compiler version is important.

GCC's external interface follows Unix conventions. Users invoke a language-specific driver program (gcc for C, g++ for C++, etc.), which interprets command arguments, calls the actual compiler, runs the assembler on the output, and then optionally runs the linker to produce a complete executable binary.

Each of the language compilers is a separate program that reads source code and outputs machine code. 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).

These are, if necessary, converted to the middle end's input representation, called GENERIC form; the middle end then gradually transforms the program towards its final form. Compiler optimizations and static code analysis techniques (such as FORTIFY_SOURCE,[21] a compiler directive that attempts to discover some buffer overflows) are applied to the code. These work on multiple representations, mostly the architecture-independent GIMPLE representation and the architecture-dependent RTL representation. Finally, machine code is produced using architecture-specific pattern matching originally based on an algorithm of Jack Davidson and Chris Fraser.

GCC was written primarily in C except for parts of the Ada front end. The distribution includes the standard libraries for Ada, C++, and Java whose code is mostly written in those languages.[22] On some platforms, the distribution also includes a low-level runtime library, libgcc, written in a combination of machine-independent C and processor-specific machine code, designed primarily to handle arithmetic operations that the target processor cannot perform directly.[23]

In May 2010, the GCC steering committee decided to allow use of a C++ compiler to compile GCC.[3] The compiler was intended to be written in C plus a subset of features from C++. In particular, this was decided so that GCC's developers could use the destructors and generics features of C++.[24]

In August 2012, the GCC steering committee announced that GCC now uses C++ as its implementation language.[25] This means that to build GCC from sources, a C++ compiler is required that understands ISO/IEC C++03 standard.

Front ends

Each front end uses a parser to produce the syntax tree abstraction of a given source file. Due to the syntax tree abstraction, source files of any of the different supported languages can be processed by the same back end. GCC started out using LALR parsers generated with Bison, but gradually switched to hand-written recursive-descent parsers; for C++ in 2004,[26] and for C and Objective-C in 2006.[27] Currently all front ends use hand-written recursive-descent parsers.

Until recently, the tree representation of the program was not fully independent of the processor being targeted.

The meaning of a tree was somewhat different for different language front ends, and front ends could provide their own tree codes. This was simplified with the introduction of GENERIC and GIMPLE, two new forms of language-independent trees that were introduced with the advent of GCC 4.0. GENERIC is more complex, based on the GCC 3.x Java front end's intermediate representation. GIMPLE is a simplified GENERIC, in which various constructs are lowered to multiple GIMPLE instructions. The C, C++ and Java front ends produce GENERIC directly in the front end. Other front ends instead have different intermediate representations after parsing and convert these to GENERIC.

In either case, the so-called "gimplifier" then converts this more complex form into the simpler SSA-based GIMPLE form that is the common language for a large number of powerful language- and architecture-independent global (function scope) optimizations.


GENERIC is an intermediate representation language used as a "middle end" while compiling source code into executable binaries. A subset, called GIMPLE, is targeted by all the front ends of GCC.

The middle stage of GCC does all of the code analysis and optimization, working independently of both the compiled language and the target architecture, starting from the GENERIC[28] representation and expanding it to Register Transfer Language (RTL). The GENERIC representation contains only the subset of the imperative programming constructs optimized by the middle end.

In transforming the source code to GIMPLE,[29] complex expressions are split into a three address code using temporary variables. This representation was inspired by the SIMPLE representation proposed in the McCAT compiler[30] by Laurie J. Hendren[31] for simplifying the analysis and optimization of imperative programs.


Optimization can occur during any phase of compilation; however, the bulk of optimizations are performed after the syntax and semantic analysis of the front end and before the code generation of the back end; thus a common, even though somewhat contradictory, name for this part of the compiler is the "middle end."

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 addition of global SSA-based optimizations on GIMPLE trees,[32] as RTL optimizations have a much more limited scope, and have less high-level information.

Some of these optimizations performed at this level 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 and automatic parallelization are also performed. Profile-guided optimization is also possible.[33]

Back end

The behavior of GCC's back end is partly specified by preprocessor macros and functions specific to a target architecture, for instance to define its 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. At any moment, the actual RTL instructions forming the program representation have to comply with the machine description of the target architecture.

The machine description file contains RTL patterns, along with operand constraints, and code snippets to output the final assembly. The constraints indicate that a particular RTL pattern might only apply (for example) to certain hardware registers, or (for example) allow immediate operand offsets of only a limited size (e.g. 12, 16, 24, … bit offsets, etc.). During RTL generation, the constraints for the given target architecture are checked. In order to issue a given snippet of RTL, it must match one (or more) of the RTL patterns in the machine description file, and satisfy the constraints for that pattern; otherwise, it would be impossible to convert the final RTL into machine code.

Towards the end of compilation, valid RTL is reduced to a strict form in which each instruction refers to real machine registers and a pattern from the target's machine description file. Forming strict RTL is a complicated task; an important step is register allocation, where real hardware registers are chosen to replace the initially assigned pseudo-registers. This is followed by a "reloading" phase; any pseudo-registers that were not assigned a real hardware register are 'spilled' to the stack, and RTL to perform this spilling is generated. Likewise, offsets that are too large to fit into an actual instruction must be broken up and replaced by RTL sequences that will obey the offset constraints.

In the final phase, the machine code is built by calling a small snippet of code, associated with each pattern, to generate the real instructions from the target's instruction set, using the final registers, offsets, and addresses chosen during the reload phase. The assembly-generation snippet may be just a string, in which case a simple string substitution of the registers, offsets, and/or addresses into the string is performed. The assembly-generation snippet may also be a short block of C code, performing some additional work, but ultimately returning a string containing the valid assembly code.


Some features of GCC include:

  • Link-time optimization optimizes across object file boundaries to directly improve the linked binary. Link-time optimization relies on an intermediate file containing the serialization of some -Gimple- representation included in the object file.[34] The file is generated alongside the object file during source compilation. Each source compilation generates a separate object file and link-time helper file. When the object files are linked, the compiler is executed again and uses the helper files to optimize code across the separately compiled object files.
  • Plugins can extend the GCC compiler directly.[35] Plugins allow a stock compiler to be tailored to specific needs by external code loaded as plugins. For example, plugins can add, replace, or even remove middle–end passes operating on Gimple representations.[36] Several GCC plugins have already been published, notably the GCC Python Plugin, which links against libpython, and allows one to invoke arbitrary Python scripts from inside the compiler. The aim is to allow GCC plugins to be written in Python. The MELT plugin provides a high-level Lisp-like language to extend GCC.[37]


The standard compiler releases since 4.6 include front ends for C (gcc), C++ (g++), Objective-C, Objective-C++, Fortran (gfortran), Java (gcj), Ada (GNAT), and Go (gccgo).[38] Also available, but not in standard are Pascal (gpc), Mercury, Modula-2, Modula-3, PL/I, D (gdc),[39] and VHDL (ghdl). A popular parallel language extension, OpenMP, is also supported. Since version 5.1, there is preliminary support for OpenACC.[40]

The Fortran front end was g77 before version 4.0, which only supports FORTRAN 77. In newer versions, g77 is dropped in favor of the new GNU Fortran front end (retaining most of g77's language extensions) that supports Fortran 95 and large parts of Fortran 2003 and Fortran 2008 as well.[41][42][43] A front-end for CHILL was dropped due to a lack of maintenance.[44]

A few experimental branches exist to support additional languages, such as the GCC UPC compiler[45] for Unified Parallel C.


GCC target processor families as of version 4.3 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:

The gcj Java compiler can target either a native machine language architecture or the Java Virtual Machine's Java bytecode.[48] When retargeting GCC to a new platform, bootstrapping is often used.


The current stable version of GCC is 5.1, which was released on April 22, 2015.[49] The release includes the new experimental libgccjit shared library for just-in-time compilation.

As of version 4.8, GCC uses C++ as its implementation language.[50]

GCC 4.6 supports many new Objective-C features, such as declared and synthesized properties, dot syntax, fast enumeration, optional protocol methods, method/protocol/class attributes, class extensions and a new GNU Objective-C runtime API. It also supports the Go programming language and includes the libquadmath library, which provides quadruple-precision mathematical functions on targets supporting the __float128 datatype. The library is used to provide the REAL(16) type in GNU Fortran on such targets.

GCC uses many standard tools in its build, including Perl, Flex, Bison, and other common tools. In addition it currently requires three additional libraries to be present in order to build: GMP, MPC, and MPFR.

The trunk concentrates the major part of the development efforts, where new features are implemented and tested. Eventually, the code from the trunk will become the next major release of GCC.


The GCC runtime exception[51] permits compilation of proprietary (and free software) programs with GCC and usage of free software plugins.


Several companies[52] make a business out of supplying and supporting GCC ports to various platforms, and chip manufacturers today consider a GCC port almost essential to the success of an architecture.[citation needed]

Revision history

Revision history[53][54]
Version Release date Notes
0.9 March 22, 1987
1.0 May 23, 1987
1.1 May 24, 1987
1.2 June 1, 1987
1.3 June 10, 1987
1.4 June 13, 1987
1.5 June 18, 1987
1.6 July 2, 1987
1.7 July 21, 1987
1.8 August 10, 1987
1.9 August 18, 1987
1.10 August 22, 1987
1.11 September 5, 1987
1.12 October 3, 1987
1.13 October 12, 1987
1.14 November 6, 1987
1.15 November 28, 1987
g++ 1.15.3 December 18, 1987
1.16 December 19, 1987
1.17 January 9, 1988
1.18 February 4, 1988
1.19 March 29, 1988
1.20 April 19, 1988
1.21 May 1, 1988
1.22 May 22, 1988
1.23 June 26, 1988
1.24 July 2, 1988
1.25 August 3, 1988
1.26 August 18, 1988
1.27 September 5, 1988
1.28 September 14, 1988
1.29 October 6, 1988
1.30 October 13, 1988
1.31 November 19, 1988
1.32 December 21, 1988
1.33 February 1, 1989
1.34 February 23, 1989
1.35 April 26, 1989
1.36 September 24, 1989
g++ 1.36.3 January 16, 1990
g++ 1.36.4 January 30, 1990
1.37 February 11, 1990
1.37.1 February 21, 1990
g++ 1.37.0 February 28, 1990
g++ 1.37.1 March 1, 1990
1.38 December 21, 1990
1.39 January 16, 1991
g++ 1.39.1 May 4, 1991
1.40 June 1, 1991
g++ 1.40.3 October 19, 1991
g++ 1.41.0 July 13, 1992
1.41 August 27, 1992
1.42 September 20, 1992
g++ 1.42.0 September 20, 1992
2.0 February 22, 1992 Supported C, C++, and Objective C. Prior to this the C++ compiler was released separately from the C compiler.
2.1 March 24, 1992
2.2 June 8, 1992
2.2.1 June 9, 1992
2.2.2 June 14, 1992
2.3 October 31, 1992
2.3.1 November 1, 1992
2.3.2 November 27, 1992
2.3.3 December 26, 1992
2.4.0 May 17, 1993
2.4.1 May 26, 1993
2.4.2 May 31, 1993
2.4.3 June 1, 1993
2.4.4 June 19, 1993
2.4.5 June 20, 1993
2.5.0 October 22, 1993
2.5.1 October 31, 1993
2.5.2 November 1, 1993
2.5.3 November 11, 1993
2.5.4 November 16, 1993
2.5.5 November 27, 1993
2.5.6 December 3, 1993
2.5.7 December 12, 1993
2.5.8 January 24, 1994
2.6.0 July 14, 1994
2.6.1 November 1, 1994
2.6.2 November 12, 1994
2.6.3 November 30, 1994
2.7.0 June 16, 1995
2.7.1 November 12, 1995
2.7.2 November 26, 1995 June 29, 1996 January 29, 1997 August 22, 1997
egcs 1.0 December 3, 1997 Added Fortran front end (g77). However, g77 was not included with releases 2.8.0 or 2.8.1.
egcs 1.0.1 January 6, 1998
2.8.0 January 7, 1998
2.8.1 March 2, 1998
egcs 1.0.2 March 16, 1998
egcs 1.0.3 May 15, 1998
egcs 1.1 September 3, 1998
egcs 1.1.1 December 1, 1998
egcs 1.1.2 March 15, 1999
2.95 July 31, 1999 Included front ends for C, C++, Objective C, CHILL, Fortran (g77), and Java (gcj)
2.95.1 August 19, 1999
2.95.2 October 24, 1999
2.95.3 March 16, 2001
3.0 June 18, 2001 CHILL compiler removed[14]
3.0.1 August 20, 2001
3.0.2 October 25, 2001
3.0.3 December 20, 2001
3.0.4 February 20, 2002
3.1 May 15, 2002 Added Ada compiler (gnat)
3.1.1 July 25, 2002
3.2 August 14, 2002
3.2.1 November 19, 2002
3.2.2 February 5, 2003
3.2.3 April 22, 2003
3.3 May 13, 2003
3.3.1 August 8, 2003
3.3.2 October 17, 2003
3.3.3 February 14, 2004
3.4.0 April 18, 2004 First version to require a C89 compiler to build
3.3.4 May 31, 2004
3.4.1 July 1, 2004
3.4.2 September 6, 2004
3.3.5 September 30, 2004
3.4.3 November 4, 2004
3.3.6 May 3, 2005
3.4.4 May 18, 2005
4.0.0 April 20, 2005 Fortran front end changed from g77 to gfortran
4.0.1 July 7, 2005
4.0.2 September 28, 2005
3.4.5 November 30, 2005
4.1.0 February 28, 2006
3.4.6 March 6, 2006
4.0.3 March 10, 2006
4.1.1 May 24, 2006
4.0.4 January 31, 2007
4.1.2 February 13, 2007
4.2.0 May 13, 2007
4.2.1 July 18, 2007 Last GPLv2 version
4.2.2 October 7, 2007
4.2.3 February 1, 2008
4.3.0 March 5, 2008
4.2.4 May 19, 2008
4.3.1 June 6, 2008
4.3.2 August 27, 2008
4.3.3 January 24, 2009
4.4.0 April 21, 2009
4.4.1 July 22, 2009
4.3.4 August 4, 2009
4.4.2 October 15, 2009
4.4.3 January 21, 2010
4.5.0 April 14, 2010 Several minor new features (new targets, new language dialects) and a couple of major new features: link-time optimization and plugins
4.4.4 April 29, 2010
4.3.5 May 22, 2010
4.5.1 July 31, 2010
4.4.5 October 1, 2010
4.5.2 December 16, 2010
4.6.0 March 25, 2011 Support added for the Go language
4.4.6 April 16, 2011
4.5.3 April 28, 2011
4.3.6 June 27, 2011
4.6.1 June 27, 2011
4.6.2 October 26, 2011
4.6.3 March 1, 2012
4.4.7 March 13, 2012
4.7.0 March 22, 2012
4.7.1 June 14, 2012
4.5.4 July 2, 2012
4.7.2 September 20, 2012
4.8.0 March 22, 2013 First version to require a C++98 compiler to build
4.7.3 April 11, 2013
4.6.4 April 12, 2013
4.8.1 May 31, 2013
4.8.2 October 16, 2013
4.9.0 April 22, 2014
4.8.3 May 22, 2014
4.9.1 July 16, 2014
4.9.2 October 30, 2014
4.8.4 December 19, 2014
5.1 April 22, 2015 Experimental just-in-time compilation shared library libgccjit released

See also


  1. ^ a b "GCC Releases". GNU Project. Retrieved 2006-12-27. 
  2. ^ "GCC Releases – GNU Project – Free Software Foundation (FSF)". 
  3. ^ a b "GCC allows C++ – to some degree". The H. June 1, 2010. 
  4. ^ "GCC Runtime Library Exception". Retrieved 2013-02-28. 
  5. ^ "Programming Languages Supported by GCC". GNU Project. Retrieved 2014-06-23. 
  6. ^ "Symbian GCC Improvement Project". Retrieved 2007-11-08. 
  7. ^ "Linux Board Support Packages". Retrieved 2008-08-07. 
  8. ^ "setting up gcc as a cross-compiler". ps2stuff. 2002-06-08. Retrieved 2008-12-12. [dead link]
  9. ^ "sh4 g++ guide". Archived from the original on 2002-12-20. Retrieved 2008-12-12. 
  10. ^ von Hagen, William (2006). The Definitive Guide to GCC. Definitive Guides (2nd ed.). Apress. p. XXVII. ISBN 978-1-4302-0219-6. So he wrote to VUCK's author asking if GNU could use it. Evidently, VUCK's developer was uncooperative, responding that the university was free but that the compiler was not. 
  11. ^ a b c Stallman, Richard (September 20, 2011). "About the GNU Project". The GNU Project. Retrieved October 9, 2011. 
  12. ^ Puzo, Jerome E., ed. (February 1986). "Gnu's Zoo". GNU'S Bulletin (Free Software Foundation) 1 (1). Retrieved 2007-08-11. 
  13. ^ Richard M. Stallman (forwarded by Leonard H. Tower, Jr.) (March 22, 1987). "GNU C compiler beta test release". Newsgroupcomp.lang.c. Retrieved October 9, 2011. 
  14. ^ Stallman, Richard M. (April 24, 1988), "Contributors to GNU CC", Internals of GNU CC (PDF), Free Software Foundation, Inc., p. 7, retrieved October 3, 2011. 
  15. ^ a b Henkel-Wallace, David (August 15, 1997), A new compiler project to merge the existing GCC forks, retrieved May 25, 2012. 
  16. ^ "Pentium Compiler FAQ". 
  17. ^ "A Brief History of GCC". 
  18. ^ "The Short History of GCC development". 
  19. ^ "GCC Steering Committee". 
  20. ^ "Linux Information Project". LINFO. Retrieved 2010-04-27. 
  21. ^ "Security Features: Compile Time Buffer Checks (FORTIFY_SOURCE)". Retrieved 2009-03-11. 
  22. ^ "languages used to make GCC". 
  23. ^ "GCC Internals". Retrieved March 1, 2010. 
  24. ^ "An email by Richard Stallman on emacs-devel". 
  25. ^ "GCC 4.8 Release Series — Changes, New Features, and Fixes". Retrieved October 4, 2013. 
  26. ^ "GCC 3.4 Release Series Changes, New Features, and Fixes". 
  27. ^ "GCC 4.1 Release Series Changes, New Features, and Fixes". 
  28. ^ "GENERIC in GNU Compiler Collection Internals". 
  29. ^ "GIMPLE in GNU Compiler Collection Internals". 
  30. ^ McCAT at the Wayback Machine (archived August 12, 2004)
  31. ^ "Laurie J. Hendren". 
  32. ^ Novillo, Diego (December 2004). "From Source to Binary: The Inner Workings of GCC". Red Hat Magazine. 
  33. ^ "Profile-guided optimization is demonstrated here". 
  34. ^ "Link Time Optimization". GCC wiki. October 3, 2009. Retrieved July 8, 2013. 
  35. ^ "Plugins". GCC online documentation. Retrieved July 8, 2013. 
  36. ^ Starynkevitch, Basile. "GCC plugins thru the MELT example" (PDF). Retrieved 2014-04-10. 
  37. ^ "About GCC MELT". Retrieved July 8, 2013. 
  38. ^ "GCC Front Ends". Retrieved November 25, 2011. 
  39. ^ "gdc project on bitbucket". Retrieved July 3, 2010. 
  40. ^ "GCC 5 Release Series". 
  41. ^ "Chart of Fortran 2003 Features supported by GNU Fortran". GNU. Retrieved 2009-06-25. 
  42. ^ "Chart of Fortran 2008 Features supported by GNU Fortran". GNU. Retrieved 2009-06-25. 
  43. ^ "Fortran 2003 Features in GNU Fortran". 
  44. ^ "PATCH] Remove chill". Retrieved July 29, 2010. 
  45. ^ "GCC UPC (GCC Unified Parallel C)". 2006-02-20. Retrieved 2009-03-11. 
  46. ^ "Hexagon Project Wiki". 
  47. ^ "sx-gcc: port gcc to nec sx vector cpu". 
  48. ^ "The GNU Compiler for the Java Programming Language". Retrieved 2010-04-22. 
  49. ^ "GCC 5.1 Released". 
  50. ^ "GCC 4.8 Release Series: Changes, New Features, and Fixes". 
  51. ^ "GCC runtime exception". FSF. Retrieved 2014-04-10. 
  52. ^ "FSF Service Directory". 
  53. ^ "GCC Releases". Retrieved March 26, 2014. 
  54. ^ "GCC Development Plan". Retrieved March 26, 2014. 

Further reading

External links