HTTP/1.1 200 OK Date: Sat, 27 Dec 2025 06:43:39 GMT Server: Apache/2.4.37 (Red Hat Enterprise Linux) OpenSSL/1.1.1k mod_qos/11.74 mod_wsgi/4.6.4 Python/3.6 mod_perl/2.0.12 Perl/v5.26.3 Vary: CF-Worker,User-Agent,Accept-Encoding Last-Modified: Sat, 11 Oct 2025 10:43:37 GMT ETag: "12d2-640dfb4e6a629-gzip" Accept-Ranges: bytes Content-Encoding: gzip Content-Security-Policy: default-src 'self' http: https: Strict-Transport-Security: max-age=16070400 Content-Length: 2201 Connection: close Content-Type: text/html; charset=utf-8

GCC: About

These pages are maintained by the GCC team and it's easy to contribute.

The web effort was originally led by Jeff Law. For the last two decades or so Gerald Pfeifer has been leading the effort, but there are many contributors .

The web pages are under git control. The pages on gcc.gnu.org are updated directly after a change has been committed. www.gnu.org is updated once a day at 4:00 -0700 (PDT).

Please send feedback, problem reports and patches to our mailing lists, ideally putting the string "[wwwdocs]" at the beginning of the mail subject.

Want to contribute? Any help concerning the items below is welcome, as are suggestions. Suggestions accompanied by patches have a higher chance of being implemented soon. ;-)

• Improve navigation, with a consistent (short) menu on every page.
• Set up a system that automatically checks the mirrors list.

  It should detect mirrors that have gone away, are persistently down, or very out of date (the last being easy to do for those carrying snapshots, harder for those with releases only). DJ Delorie <dj@redhat.com> has some scripts to do this already.

---

Using the git repository

Assuming you have both git and SSH installed, you can check out the web pages via

git clone git+ssh://username@gcc.gnu.org/git/gcc-wwwdocs.git

where username is your user name at gcc.gnu.org.

For anonymous access, use

git clone https://gcc.gnu.org/git/gcc-wwwdocs.git

Validating a change

To validate any changes, you can use the W3 Validator. Just use the "Validate by File Upload" functionality.

Checking in a change

We recommend you list files explicitly to avoid accidental checkins and prefer that each checkin be of a complete, single logical change.

1. Sync your sources with the master repository via "git pull". This will also identify any files in your local tree that you have modified.
2. We recommend reviewing the output of "git diff".
3. Use "git commit" and "git push origin master" to check in the patch.
4. Upon checkin a message will be sent to the gcc-cvs-wwwdocs mailing list.

As changes are checked in, the respective pages are preprocessed via the script wwwdocs/bin/preprocess which in turn uses a tool called MetaHTML. Among others, this preprocessing adds CSS style sheets, XML and HTML headers, and our standard footer. The MetaHTML style sheet is in wwwdocs/htdocs/style.mhtml.