This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: documenting changes to the front-end interface (was: Removemake_function_rtl)
- To: Fergus Henderson <fjh at cs dot mu dot oz dot au>
- Subject: Re: documenting changes to the front-end interface (was: Removemake_function_rtl)
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Date: Thu, 11 Jan 2001 12:29:11 +0000 (GMT)
- cc: Mark Mitchell <mark at codesourcery dot com>, <gcc at gcc dot gnu dot org>, <gcc-patches at gcc dot gnu dot org>
On Thu, 11 Jan 2001, Fergus Henderson wrote:
> So, what's the policy? Should changes that affect language
> front-ends be documented in gcc/LANGUAGES, or not?
In principle, the whole front end interface should be documented. OK to
commit the following patch to projects/index.html?
Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/index.html,v
retrieving revision 1.9
diff -u -r1.9 index.html
--- index.html 2000/12/22 17:52:15 1.9
+++ index.html 2001/01/11 12:27:22
@@ -115,6 +115,13 @@
for these builtins should be discussed with the gcc and libc-alpha
lists.</li>
+<li>Fully document the interface of front ends to GCC (that is, the
+<code>tree</code> interfaces, and the various functions, hooks, etc.,
+that a front end must or may provide). <code>gcc/c-tree.texi</code>
+includes some of this information; <code>gcc/LANGUAGES</code> contains
+incomplete information about changes that have been made to this
+interface.</li>
+
</ul>
<h2>Better builtin string functions</h2>
--
Joseph S. Myers
jsm28@cam.ac.uk