We strongly encourage contributions of code, bugfixes, new optimizations, new features, documentation updates, web page improvements, etc. for GCC
There are certain legal requirements and style issues which all contributions must meet.
All contributions must conform to the GNU Coding Standards. There are also some additional coding conventions for GCC. Submissions which do not conform to the standards will be returned with a request to reformat the changes.
Before we can accept code contributions from you, we need a copyright assignment form filled out and filed with the FSF.
See some documentation by the FSF for details and contact us (either via the gcc@gcc.gnu.org list or the GCC maintainer that is taking care of your contributions) to obtain the relevant forms.
Small changes can be accepted without a copyright assignment form on file.
Every patch must have several pieces of information before we can properly evaluate it.
The patch itself. If you are accessing the
CVS repository at gcc.gnu.org, use
"cvs update; cvs diff -c3p
"; else, use
"diff -c3p OLD NEW
" or
"diff -up OLD NEW
".
If your version of diff does not support these options, then get
the latest version of GNU diff.
We accept patches as plain text (preferred for the compilers themselves), MIME attachments (preferred for the web pages), or as uuencoded gzipped text.
When you have all these pieces, bundle them up in a mail message and send it to gcc-patches@gcc.gnu.org. All patches and related discussion should be sent to the gcc-patches mailinglist. For further information on the GCC CVS repository, see the Anonymous read-only CVS access and Read-write CVS access pages.
If you do not receive a response to a patch that you have submitted within a month or so, it may be a good idea to chase it by sending a follow-up email to gcc-patches@gcc.gnu.org. Patches can occasionally fall through the cracks. Please be sure to include in the follow-up email the URL of the entry in the mailing list archive of the original submission.