A front end for a language in GCC has the following parts:
gcccontaining source files for that front end. See The Front End
Directory, for details.
gcc/doc/contrib.texi. If the details are in that front end's own manual then there should be a link to that manual's list in
gcc/doc/standards.texi. This may be a link to such information in the front end's own manual.
options supported, in
gcc.cfor source file suffixes for that language.
gcc/testsuiteor runtime library directories. FIXME: document somewhere how to write test suite harnesses.
gccdirectory. FIXME: document this further.
If the front end is added to the official GCC CVS repository, the following are also necessary:
gcc/gccbug.in, and in
gnats.htmlon the GCC web site, as well as being added to the GNATS database.
frontends.html, with any relevant links on
readings.html. (Front ends that are not an official part of GCC may also be listed on
frontends.html, with relevant links.)
index.html, and possibly an announcement on the email@example.com mailing list.
maintainer-scripts/update_web_docs(see Texinfo Manuals) and the online manuals should be linked to from
maintainer-scripts/gcc_releaseshould be updated to generate appropriate tarballs for this front end.
maintainer-scripts/update_versionshould be updated accordingly.
CVSROOT/modulesin the GCC CVS repository should be updated.