Differences between revisions 46 and 47
Revision 46 as of 2013-01-23 09:59:19
Size: 5624
Comment: 10 steps guide
Revision 47 as of 2014-05-12 20:29:10
Size: 5637
Editor: TobiasBurnus
Comment: Change HTTP to HTTPS
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
    GCC is owned by the [[http://www.fsf.org|Free Software Foundation (FSF)]], as such, all contributors must assign their copyright to the FSF before any of their changes are accepted. The copyright assignment process is described in [[http://gcc.gnu.org/contribute.html#legal|Contributing to GCC]]. (See also [[http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html|copyright papers]] and [[http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright|forms]].)     GCC is owned by the [[https://www.fsf.org|Free Software Foundation (FSF)]], as such, all contributors must assign their copyright to the FSF before any of their changes are accepted. The copyright assignment process is described in [[https://gcc.gnu.org/contribute.html#legal|Contributing to GCC]]. (See also [[http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html|copyright papers]] and [[http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright|forms]].)
Line 19: Line 19:
    * SVN: [[http://gcc.gnu.org/svn.html]] [[http://gcc.gnu.org/wiki/SvnHelp]]
    * Git: http://gcc.gnu.org/wiki/GitMirror
    * SVN: [[https://gcc.gnu.org/svn.html]] [[https://gcc.gnu.org/wiki/SvnHelp]]
    * Git: https://gcc.gnu.org/wiki/GitMirror
Line 22: Line 22:
 1. Building GCC: http://gcc.gnu.org/install/  1. Building GCC: https://gcc.gnu.org/install/
Line 32: Line 32:
 1. [[http://gcc.gnu.org/contribute.html#patches|Submitting patches]]  1. [[https://gcc.gnu.org/contribute.html#patches|Submitting patches]]
Line 34: Line 34:
 1. [[http://gcc.gnu.org/svnwrite.html|Committing patches]]  1. [[https://gcc.gnu.org/svnwrite.html|Committing patches]]
Line 62: Line 62:
 * [[http://gcc.gnu.org/onlinedocs/gccint/|GCC internals]]
 * [[http://gcc.gnu.org/onlinedocs/cppinternals/|CPP internals]]
 * [[https://gcc.gnu.org/onlinedocs/gccint/|GCC internals]]
 * [[https://gcc.gnu.org/onlinedocs/cppinternals/|CPP internals]]
Line 89: Line 89:
When using [[http://gcc.gnu.org/bugzilla|Bugzilla]], GCC maintainers (those having at least write after approval status to GCC trunk) [[http://gcc.gnu.org/ml/gcc/2009-10/msg00519.html|should preferably]] use their ''username''`@gcc.gnu.org` account to log in [[http://gcc.gnu.org/bugzilla|Bugzilla]]. When using [[https://gcc.gnu.org/bugzilla|Bugzilla]], GCC maintainers (those having at least write after approval status to GCC trunk) [[https://gcc.gnu.org/ml/gcc/2009-10/msg00519.html|should preferably]] use their ''username''`@gcc.gnu.org` account to log in [[https://gcc.gnu.org/bugzilla|Bugzilla]].

Welcome to the Getting Started section of the GCC Wiki

We are constantly looking for new developers who are willing to donate their time to advance GCC.

This section contains collected information geared towards folks who are new to GCC and may be feeling a bit lost in the barbaric jungles of GCC's source code. Although we are continuously trying to improve GCC's internal modularity and interfaces, the fact remains that GCC is about 20 years old, fairly large and we need to keep it working on the multitude of supported architectures and languages. So, getting to work with GCC can be a challenge.

Everyone is welcome to add links to tutorials, HOWTOs, cheat sheets, etc that may be floating around the net.

Basics: Contributing to GCC in 10 easy steps

  1. The most important formality that you need to go through: Copyright assignment.

  2. Accessing the sources:
  3. Building GCC: https://gcc.gnu.org/install/

  4. Testing GCC and Compile time and memory utilization testing

  5. Debugging GCC

  6. Formatting code for GCC

  7. How to communicate with the GCC community effectively

  8. Submitting patches

  9. Committing patches

  10. Profit!

Tutorials, HOWTOs

Internal documentation

Dealing with the source code

Structure Of GCC

Reporting and correcting bugs

When using Bugzilla, GCC maintainers (those having at least write after approval status to GCC trunk) should preferably use their username@gcc.gnu.org account to log in Bugzilla.

None: GettingStarted (last edited 2017-09-13 11:25:27 by NathanSidwell)