Differences between revisions 47 and 48
Revision 47 as of 2014-05-12 20:29:10
Size: 5637
Editor: TobiasBurnus
Comment: Change HTTP to HTTPS
Revision 48 as of 2014-10-06 21:22:51
Size: 5996
Comment: improve 10 steps
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
    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]].)     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]]. In a nutshell, send an email to <assign@gnu.org> and explain that you want to contribute code to GCC and what is your employment status (student, employed by a company, self-employed, ...) and they will send you a form to sign. If they don't reply in 3-5 days, insist. If there is still no reply, write to <gcc@gcc.gnu.org> and explain your case.
This process requires some patience but while you wait, you can continue with the next steps.
Line 18: Line 19:
 1. Accessing the sources:
    * SVN: [[https://gcc.gnu.org/svn.html]] [[https://gcc.gnu.org/wiki/SvnHelp]]
    * Git: https://gcc.gnu.org/wiki/GitMirror
 1. Accessing the sources, you can choose between:
    * [[https://gcc.gnu.org/svn.html|Subversion]] (see also the tips about [[https://gcc.gnu.org/wiki/SvnHelp|using subversion for GCC development]])
    * [[https://gcc.gnu.org/wiki/GitMirror|Git]]
Line 22: Line 23:
 1. Building GCC: https://gcc.gnu.org/install/  1. [[InstallingGCC|Building GCC]] (you do not actually need to install GCC to test it, it is enough to build it)
Line 24: Line 25:
 1. [[Testing_GCC|Testing GCC]] and [[PerformanceTesting|Compile time and memory utilization testing]]  1. [[Testing_GCC|Testing GCC]]

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.

    • GCC is owned by the 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 Contributing to GCC. In a nutshell, send an email to <assign@gnu.org> and explain that you want to contribute code to GCC and what is your employment status (student, employed by a company, self-employed, ...) and they will send you a form to sign. If they don't reply in 3-5 days, insist. If there is still no reply, write to <gcc@gcc.gnu.org> and explain your case.

This process requires some patience but while you wait, you can continue with the next steps.

  1. Accessing the sources, you can choose between:
  2. Building GCC (you do not actually need to install GCC to test it, it is enough to build it)

  3. Testing GCC

  4. Debugging GCC

  5. Formatting code for GCC

  6. How to communicate with the GCC community effectively

  7. Submitting patches

  8. Committing patches

  9. 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)