Jump to content

Toggle sidebar
Search Go

 Create account
Personal tools




Contents
 hide

(Top)

History

EGCS fork

Supported languages

Design

o
 Front ends

GENERIC and GIMPLE

Optimization

Back end

C++ Standard Library (libstdc++)

Other features

Architectures

License


 See also

References

Further reading

External links

Official

Other

GNU Compiler Collection

47 languages
 Article
 Talk
 Read
 Edit
 View history
From Wikipedia, the free encyclopedia
This article relies excessively on references to primary sources. Please
improve this article by adding secondary or tertiary sources.
Find sources: "GNU Compiler
Collection" – news · newspapers · books · scholar · JSTOR (January 2022) (Learn how
and when to remove this template message)
 GNU Compiler Collection

Screenshot of GCC 10.2 compiling its own source code

Original author(s) Richard Stallman

Developer(s) GNU Project

Initial release March 22, 1987; 35 years ago[1]

Stable release 12.2[2]   / 19 August 2022

 gcc.gnu.org/git/gcc.git 
Repository

Written in C, C++[3]

Operating system Cross-platform

Platform GNU and many others

 Size ~15 million LOC[4]

Available in English

Type Compiler

License GPLv3+ with GCC Runtime Library Exception[5]

Website gcc.gnu.org

The GNU Compiler Collection (GCC) is an optimizing compiler produced by the GNU

Project supporting various programming languages, hardware
architectures and operating systems. The Free Software Foundation (FSF) distributes
GCC as free software under the GNU General Public License (GNU GPL). GCC is a
key component of the GNU toolchain and the standard compiler for most projects
related to GNU and the Linux kernel. With roughly 15 million lines of code in 2019, GCC
is one of the biggest free programs in existence. [4] It has played an important role in the
growth of free software, as both a tool and an example.
When it was first released in 1987 by Richard Stallman, GCC 1.0 was named the GNU
C Compiler since it only handled the C programming language.[1] It was extended to
compile C++ in December of that year. Front ends were later developed for Objective-
C, Objective-C++, Fortran, Ada, D and Go, among others.
[6]
 The OpenMP and OpenACC specifications are also supported in the C and C++
compilers.[7][8]
GCC has been ported to more platforms and instruction set architectures than any other
compiler, and is widely deployed as a tool in the development of both free
and proprietary software. GCC is also available for many embedded systems,
including ARM-based and Power ISA-based chips.
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 most Linux distributions. Most BSD family operating systems also
switched to GCC shortly after its release, although since
then, FreeBSD, OpenBSD and Apple macOS have moved to the Clang compiler,
[9]
 largely due to licensing reasons.[10][11][12] GCC can also compile code
for Windows, Android, iOS, Solaris, HP-UX, AIX and DOS.[13]

History[edit]
In late 1983, 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) for permission to use that software for GNU.
When Tanenbaum advised him that the compiler was not free, and that only the
university was free, Stallman decided to work on a different compiler. [14] His initial plan
was to rewrite an existing compiler from Lawrence Livermore National
Laboratory from Pastel to C with some help from Len Tower and others.[15][16] 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 64 KB,
and concluded he would have to write a new compiler from scratch. [15] None of the Pastel
compiler code ended up in GCC, though Stallman did use the C front end he had
written.[15][17]
GCC was first released March 22, 1987, available by FTP from MIT.[18] Stallman was
listed as the author but cited others for their contributions, including Tower for "parts of
the parser, RTL generator, RTL definitions, and of the Vax machine description", Jack
Davidson and Christopher W. Fraser for the idea of using RTL as an intermediate
language, and Paul Rubin for writing most of the preprocessor. [19] Described as the "first
free software hit" by Peter H. Salus, the GNU compiler arrived just at the time when Sun
Microsystems was unbundling its development tools from its operating system, selling
them separately at a higher combined price than the previous bundle, which led many of
Sun's users to buy or download GCC instead of the vendor's tools. [20] While Stallman
considered GNU Emacs as his main project, by 1990, GCC supported thirteen
computer architectures, was outperforming several vendor compilers, and was used
commercially by several companies.[21]
EGCS fork[edit]
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, as the project favored stability over new features. [22] The
FSF kept such close control on what was added to the official version of GCC 2.x
(developed since 1992) that GCC was used as one example of the "cathedral"
development model in Eric S. Raymond's essay The Cathedral and the Bazaar.
In 1997, a group of developers formed the Experimental/Enhanced GNU Compiler
System (EGCS) to merge several experimental forks into a single project. [22][17] The basis
of the merger was a development snapshot of GCC (taken around the 2.7.2 and later
followed up to 2.8.1 release). Mergers included g77 (Fortran), PGCC (P5 Pentium-
optimized GCC),[17] many C++ improvements, and many new architectures and operating
system variants.[23]
While both projects followed each other's changes closely, EGCS development proved
considerably more vigorous, 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. [24][17] GCC has since been
maintained by a varied group of programmers from around the world under the direction
of a steering committee.[25]
GCC 3 (2002) removed a front-end for CHILL due to a lack of maintenance.[26]
Before version 4.0 the Fortran front end was  g77 , which only supported FORTRAN 77,
but later was dropped in favor of the new GNU Fortran front end that supports Fortran
95 and large parts of Fortran 2003 and Fortran 2008 as well.[27][28]
As of version 4.8, GCC is implemented in C++.[29]
Support for Cilk Plus existed from GCC 5 to GCC 7.[30][31]
GCC has been ported to a wide variety of instruction set architectures, and is widely
deployed as a tool in the development of both free and proprietary software. GCC is
also available for many embedded systems, including Symbian (called gcce),[32] ARM-
based, and Power ISA-based chips.[33] The compiler can target a wide variety of
platforms, including video game consoles such as the PlayStation 2,[34] Cell SPE of
PlayStation 3,[35] and Dreamcast.[36] It has been ported to more kinds of processors and
operating systems than any other compiler.[37][self-published source?][better  source  needed]

Supported languages[edit]
As of May 2021, the recent 11.1 release of GCC includes front ends for C ( gcc ), C+
+ ( g++ ), Objective-C, Fortran ( gfortran ), Ada (GNAT), Go ( gccgo ) and D ( gdc , since
9.1)[38] programming languages,[39] with the OpenMP and OpenACC parallel language
extensions being supported since GCC 5.1.[8][40] Versions prior to GCC 7 also
supported Java ( gcj ), allowing compilation of Java to native machine code. [41] Modula-
2 support, previously offered by third parties, will be merged into GCC 13. [42]
Regarding language version support for C++ and C, since GCC 11.1 the default target
is gnu++17, a superset of C++17, and gnu11, a superset of C11, with strict standard
support also available. GCC also provides experimental support for C++20 and
upcoming C++23.[43]
Third-party front ends exist for many languages, such as Pascal ( gpc ), Modula-3,
and VHDL ( GHDL ).[39] A few experimental branches exist to support additional languages,
such as the GCC UPC compiler for Unified Parallel C[44] or Rust.[45][46][47][better  source  needed]

Design[edit]

Overview of GCC's extended compilation pipeline, including specialized programs like

the preprocessor, assembler and linker.
GCC follows the 3-stage architecture typical of multi-language and multi-CPU compilers. All program trees are
converted to a common abstract representation at the "middle end", allowing code optimization and binary
code generation facilities to be shared by all languages.

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,[48] 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 and C++ whose code is mostly written in those
languages.[49][needs update] 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.[50]
GCC uses many additional tools in its build, many of which are installed by default by
many Unix and Linux distributions (but which, normally, aren't present in Windows
installations), including Perl,[further explanation needed] 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.[51]
In May 2010, the GCC steering committee decided to allow use of a C++ compiler to
compile GCC.[52] The compiler was intended to be written mostly 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++.[53]
In August 2012, the GCC steering committee announced that GCC now uses C++ as its
implementation language.[54] This means that to build GCC from sources, a C++ compiler
is required that understands ISO/IEC C++03 standard.
On May 18, 2020, GCC moved away from ISO/IEC C++03 standard to ISO/IEC C+
+11 standard (i.e. needed to compile, bootstrap, the compiler itself; by default it
however compiles later versions of C++).[55]
Front ends[edit]

Front ends consist of preprocessing, lexical analysis, syntactic analysis (parsing) and semantic analysis. The
goals of compiler front ends are to either accept or reject candidate programs according to the language
grammar and semantics, identify errors and handle valid program representations to later compiler stages. This
example shows the lexer and parser steps performed for a simple program written in C.

Each front end uses a parser to produce the abstract syntax tree 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,[56] and for C and Objective-C in 2006.[57] As of 2021 all front ends
use hand-written recursive-descent parsers.
Until GCC 4.0 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 and GIMPLE[edit]
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[58] 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, [59] 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 [60] by Laurie J.
Hendren[61] for simplifying the analysis and optimization of imperative programs.
Optimization[edit]
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,[62] 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.[63]
Back end[edit]
This section does not cite any sources. Please help improve this
section by adding citations to reliable sources. Unsourced material may be
challenged and removed. (May 2020) (Learn how and when to remove this template
message)

The 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.
C++ Standard Library (libstdc++)[edit]
The GCC project includes an implementation of the C++ Standard Library called
libstdc++,[64] licensed under the GPLv3 License with an exception to link closed source
application when sources are built with GCC.[65] The current version is 11[when?].
Other features[edit]
Some features of GCC include:
Link-time optimization
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. [citation
needed]
 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
Plugins extend the GCC compiler directly.[66] 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.[67] Several GCC plugins have already been published,
notably:

 The 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.[68]
The support of plugins was once a contentious issue in 2007. [69]
C++ transactional memory
The C++ language has an active proposal for transactional memory. It can be
enabled in GCC 6 and newer when compiling with  -fgnu-tm .[7][70]
Unicode identifiers
Although the C++ language requires support for non-ASCII Unicode
characters in identifiers, the feature has only been supported since GCC 10. As
with the existing handling of string literals, the source file is assumed to be
encoded in UTF-8. The feature is optional in C, but has been made available too
since this change.[71][72]
C extensions
GNU C extends the C programming language with several non-standard-
features, including nested functions[73] and  typeof  expressions.[74]

Architectures[edit]

GCC compiling Hello World on Windows

The primary supported (and best tested) processor families are

64- and 32-bit ARM, 64- and 32-bit x86_64 and x86 and 64-
bit PowerPC and SPARC.[75]
GCC target processor families as of version 11.1 include: [76]

 AArch64
 Alpha
 ARM
 AVR
 Blackfin
 eBPF
 Epiphany (GCC 4.8)
 H8/300
 HC12
 IA-32 (x86)
 IA-64 (Intel Itanium)
 MIPS
 Motorola 68000
  MSP430
 Nvidia GPU
 Nvidia PTX
 PA-RISC
 PDP-11
 PowerPC
 R8C / M16C / M32C
 RISC-V
 SPARC
 SuperH
 System/390 / zSeries
 VAX
 x86-64
Lesser-known target processors supported in the standard
release have included:

 68HC11
 A29K
 C6x
 CR16
 D30V
 DSP16xx
 ETRAX CRIS
 FR-30
 FR-V
 IBM ROMP
 Intel i960
 IP2000
 M32R
 MCORE
 MIL-STD-1750A
 MMIX
 MN10200
 MN10300
 Motorola 88000
 NS32K
 RL78
 Stormy16
 V850
 Xtensa
Additional processors have been supported by GCC versions
maintained separately from the FSF version:
  Cortus APS3
 ARC
 AVR32
 C166 and C167
 D10V
 EISC
 eSi-RISC
 Hexagon[77]
 LatticeMico32
 LatticeMico8
 MeP
 MicroBlaze
 Motorola 6809
 MSP430
 NEC SX architecture[78]
 Nios II and Nios
 OpenRISC
 PDP-10
 PIC24/dsPIC
 PIC32
 Propeller
 Saturn (HP48XGCC)
 System/370
 TIGCC (m68k variant)
 TMS9900
 TriCore
 Z8000
 ZPU
The GCJ Java compiler can target either a native machine
language architecture or the Java virtual machine's Java
bytecode.[79] When retargeting GCC to a new
platform, bootstrapping is often used. Motorola 68000, Zilog Z80,
and other processors are also targeted in the GCC versions
developed for various Texas Instruments, Hewlett Packard,
Sharp, and Casio programmable graphing calculators. [80]

License[edit]
GCC is licensed under the GNU General Public License version 3.
[81]
 The GCC runtime exception permits compilation of proprietary
programs (in addition to free software) with GCC. This does not
impact the license terms of GCC source code.[82]
See also[edit]

 Free and open-source software portal

 Computer programming portal

 List of compilers
 MinGW
 LLVM/Clang

References[edit]
1. ^ Jump up to:a b "GCC Releases". GNU Project. Retrieved July
24,  2020.
2. ^ "GCC 12.2 Released"; author name string: Richard Biener;
publication date: 19 August 2022; retrieved: 19 August 2022.
3. ^ "GCC Coding Conventions - GNU Project". gcc.gnu.org.
Retrieved February 7,  2022.
4. ^ Jump up to:a b Víctor Rodríguez (October 1, 2019). "Cutting
Edge Toolchain (Latest Features in GCC/GLIBC)". youtube.com.
Linux Foundation. Archived from the original on November 7,
2021. Retrieved  January 19,  2021.
5. ^ "GCC Runtime Library Exception". Retrieved July 24, 2020.
6. ^ "Programming Languages Supported by GCC". GNU Project.
Retrieved June 23, 2014.
7. ^ Jump up to:a b "GCC 6 Release Series — Changes, New
Features, and Fixes - GNU Project". gcc.gnu.org.
8. ^ Jump up to:a b "OpenACC - GCC Wiki". gcc.gnu.org.
9. ^ "The LLVM Compiler Infrastructure Project".  llvm.org.
10. ^ "Apple's GPLv3 purge".  meta.ath0.com. Retrieved January
12,  2021.
11. ^ Linnemann, Reid (June 20, 2012). "Why Clang".
Retrieved January 12, 2021.
12. ^ "August 29, 2007: FreeBSD Foundation Newsletter, August 29,
2007". October 11, 2007. Archived from  the original on October
11, 2007. Retrieved January 12, 2021.
13. ^ "Installing GCC: Binaries - GNU Project - Free Software
Foundation (FSF)". gcc.gnu.org. Retrieved  January 12,  2021.
14. ^ 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.
15. ^ Jump up to:a b c Stallman, Richard (September 20, 2011). "About
the GNU Project". The GNU Project. Retrieved  October 9,  2011.
16. ^ Puzo, Jerome E., ed. (February 1986). "Gnu's Zoo". GNU's
Bulletin. Free Software Foundation.  1 (1). Retrieved August
11,  2007.
17. ^ Jump up to:a b c d von Hagen, William (2006). The Definitive
Guide to GCC. Definitive Guides (2nd  ed.). Apress.
p. XXVII. ISBN 978-1-4302-0219-6.
18. ^ Richard M. Stallman (forwarded by Leonard H. Tower Jr.)
(March 22, 1987).  "GNU C compiler beta test
release".  Newsgroup: comp.lang.c. Retrieved  October 9,  2011.
19. ^ Stallman, Richard M. (June 22, 2001) [First published
1988],  "Contributors to GNU CC",  Using and Porting the GNU
Compiler Collection (GCC), Free Software Foundation, Inc., p.  7,
retrieved June 18, 2015.
20. ^ Salus, Peter H.  (2005). "Chapter 10. SUN and gcc". The
Daemon, the Gnu and the Penguin.  Groklaw.
21. ^ Garfinkel, Simson L. (August 6, 1990).  "Get ready for GNU
software". Computerworld. p. 102.
22. ^ Jump up to:a b Henkel-Wallace, David (August 15, 1997),  A new
compiler project to merge the existing GCC forks, retrieved May
25,  2012.
23. ^ "The Short History of GCC
development". www.softpanorama.org. Retrieved January
24,  2021.
24. ^ "History - GCC Wiki".  gcc.gnu.org. Retrieved September
28,  2020.
25. ^ "GCC steering committee - GNU Project".  gcc.gnu.org.
26. ^ "PATCH] Remove chill". gcc.gnu.org. Retrieved  July 29,  2010.
27. ^ "Chart of Fortran 2003 Features supported by GNU
Fortran". GNU. Retrieved June 25, 2009.
28. ^ "Chart of Fortran 2008 Features supported by GNU
Fortran". GNU. Retrieved June 25, 2009.
29. ^ "GCC 4.8 Release Series — Changes, New Features, and
Fixes - GNU Project".  gcc.gnu.org.
30. ^ "GCC 5 Release Series — Changes, New Features, and
Fixes".  gcc.gnu.org.
31. ^ "GCC 8 Release Series — Changes, New Features, and
Fixes".  gcc.gnu.org.
32. ^ "Symbian GCC Improvement Project". Retrieved  November
8, 2007.
33. ^ "Linux Board Support Packages". Archived from the original  on
June 7, 2011. Retrieved  January 24,  2021.
34. ^ "setting up gcc as a cross-compiler". ps2stuff. June 8, 2002.
Archived from  the original on December 11, 2008.
Retrieved December 12,  2008.
35. ^ "CompileFarm - GCC Wiki". gcc.gnu.org.
36. ^ "sh4 g++ guide". Archived from  the original on December 20,
2002. Retrieved  December 12, 2008.
37. ^ "Linux Information Project". LINFO. Retrieved April
27,  2010. The GCC has been ported to (i.e., modified to run on)
more than 60 platforms, which is more than for any other
compiler.
38. ^ "The D Language Front-End Finally Merged Into GCC 9 -
Phoronix".  phoronix.com. Retrieved January 19, 2021.
39. ^ Jump up to:a b "GCC Front Ends". gnu.org. Retrieved  November
25,  2011.
40. ^ "GCC 5 Release Series — Changes, New Features, and Fixes -
GNU Project". gcc.gnu.org.
41. ^ "GCC 7 Release Series". gnu.org. Retrieved  March 20,  2018.
42. ^ Proven, Liam (December 16, 2022). "GCC 13 to support
Modula-2: Follow-up to Pascal lives on in FOSS form".
Retrieved December 19,  2022.
43. ^ "C++ Standards Support in GCC". Retrieved  May 17, 2021.
44. ^ "GCC UPC (GCC Unified Parallel C)". Intrepid Technology, Inc.
February 20, 2006. Retrieved  March 11,  2009.
45. ^ "GCC Front-End For Rust". Retrieved January 6, 2023.
46. ^ "GCC Front-End for Rust (Github)". GitHub. January 5, 2023.
Retrieved January 6, 2023.
47. ^ Spengler, Brad (January 12, 2021).  "Open Source Security, Inc.
Announces Funding of GCC Front-End for Rust".
48. ^ "Security Features: Compile Time Buffer Checks
(FORTIFY_SOURCE)". fedoraproject.org. Retrieved  March
11,  2009.
49. ^ "languages used to make GCC". Archived from the original  on
May 27, 2008. Retrieved  September 14,  2008.
50. ^ "GCC Internals". GCC.org. Retrieved March 1, 2010.
51. ^ "Prerequisites for GCC - GNU Project".  gcc.gnu.org.
Retrieved September 5, 2021.
52. ^ "GCC allows C++  – to some degree". The H. June 1, 2010.
53. ^ "Re: Efforts to attract more users?". lists.gnu.org.
54. ^ "GCC 4.8 Release Series: Changes, New Features, and Fixes".
Retrieved October 4, 2013.
55. ^ "bootstrap: Update requirement to C++11".  GitHub.
Retrieved May 18,  2020.
56. ^ "GCC 3.4 Release Series — Changes, New Features, and
Fixes - GNU Project".  gcc.gnu.org.
57. ^ "GCC 4.1 Release Series — Changes, New Features, and
Fixes - GNU Project".  gcc.gnu.org.
58. ^ "GENERIC (GNU Compiler Collection (GCC)
Internals)". gcc.gnu.org.
59. ^ "GIMPLE (GNU Compiler Collection (GCC)
Internals)". gcc.gnu.org.
60. ^ "McCAT". Archived from the original on August 12, 2004.
Retrieved September 14, 2017.
61. ^ "Laurie Hendren's Home Page". www.sable.mcgill.ca.
62. ^ Novillo, Diego (December 2004).  "From Source to Binary: The
Inner Workings of GCC". Red Hat Magazine. Archived from  the
original on April 1, 2009.
63. ^ "Installing GCC: Building - GNU Project".  gcc.gnu.org.
64. ^ "The GNU C++ Library". GNU Project. Retrieved  February
21,  2021.
65. ^ "License". GNU Project. Retrieved February 21, 2021.
66. ^ "Plugins". GCC online documentation. Retrieved  July 8,  2013.
67. ^ Starynkevitch, Basile.  "GCC plugins thru the MELT
example"  (PDF).  Archived  (PDF) from the original on April 13,
2014. Retrieved  April 10,  2014.
68. ^ "About GCC MELT". Archived from the original on July 4, 2013.
Retrieved July 8, 2013.
69. ^ "GCC unplugged [LWN.net]".  lwn.net.
70. ^ "TransactionalMemory - GCC Wiki".  gcc.gnu.org.
71. ^ "Lewis Hyatt - [PATCH] wwwdocs: Document support for
extended identifiers added to GCC".  gcc.gnu.org.
Retrieved March 27, 2020.
72. ^ "Recommendations for extended identifier characters for C and
C++".  www.open-std.org. Retrieved March 27, 2020.
73. ^ "C Extensions (Using the GNU Compiler Collection
(GCC))". gcc.gnu.org. Retrieved  January 12,  2022.
74. ^ "Typeof - Using the GNU Compiler Collection
(GCC)". gcc.gnu.org. Retrieved  January 12,  2022.
 75. ^ "GCC 12 Release Criteria". gcc.gnu.org. October 26, 2022.
Retrieved January 27, 2023.
76. ^ "Option Summary (Using the GNU Compiler Collection
(GCC))". gcc.gnu.org. Retrieved  August 21,  2020.
77. ^ "Hexagon Project Wiki". Archived from the original  on March
23, 2012. Retrieved May 19,  2011.
78. ^ "Google Code Archive - Long-term storage for Google Code
Project Hosting". code.google.com.
79. ^ "The GNU Compiler for the Java Programming Language".
Archived from  the original on May 9, 2007. Retrieved April
22,  2010.
80. ^ graphing calculators#programming
81. ^ "Using the GNU Compiler Collection".  gnu.org.
Retrieved November 5,  2019.
82. ^ "GCC Runtime Exception". FSF. Retrieved  April 10,  2014.

Further reading[edit]
 Using the GNU Compiler Collection (GCC), Free
Software Foundation, 2008.
 GNU Compiler Collection (GCC) Internals, Free
Software Foundation, 2008.
 An Introduction to GCC, Network Theory Ltd., 2004
(Revised August 2005). ISBN 0-9541617-9-3.
 Arthur Griffith, GCC: The Complete Reference. McGraw
Hill / Osborne, 2002. ISBN 0-07-222405-3.

External links[edit]

Wikimedia Commons has media related to GCC.

Wikibooks has a book on the topic of: GNU C Compiler Internals

Official[edit]
 Official website 
 GCC Release Timeline
 GCC Development Plan
Other[edit]
 Collection of GCC 4.0.2 architecture and internals
documents at I.I.T. Bombay
 Kerner, Sean Michael (March 2, 2006). "New GCC
Heavy on Optimization". internetnews.com
  Kerner, Sean Michael (April 22, 2005). "Open Source
GCC 4.0: Older, Faster". internetnews.com. Archived
from the original on September 17, 2006.
Retrieved October 21, 2006
 From Source to Binary: The Inner Workings of GCC , by
Diego Novillo, Red Hat Magazine, December 2004
 A 2003 paper on GENERIC and GIMPLE
 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
 EGCS 1.0 announcement
 EGCS 1.0 features list
 Fear of Forking, an essay by Rick Moen recording
seven well-known forks, including the GCC/EGCS one
show
v

e
GNU Project

show
v

e
Free and open-source software

Authority control: National

 Germany
libraries 
Categories: 
 1987 software
 C (programming language) compilers
 C++ compilers
 Compilers
 Cross-platform free software
 Fortran compilers
 Free compilers and interpreters
 GNU Project software
 Java development tools
 Pascal (programming language) compilers
 Software that was rewritten in C++
 Free software programmed in C++
 Software using the GPL license
 Unix programming tools
 This page was last edited on 31 January 2023, at 01:21 (UTC).
 Text is available under the Creative Commons Attribution-ShareAlike License
3.0; additional terms may apply. By using this site, you agree to the Terms of
Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia
Foundation, Inc., a non-profit organization.
 Privacy policy

 About Wikipedia

 Disclaimers

 Contact Wikipedia

 Mobile view

 Developers

 Statistics

 Cookie statement