This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: IA-64 non-call exceptions
- To: Andrew Haley <aph at cambridge dot redhat dot com>
- Subject: Re: IA-64 non-call exceptions
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Date: Tue, 19 Jun 2001 23:46:17 +0100 (BST)
- cc: <gcc-patches at gcc dot gnu dot org>, <java at gcc dot gnu dot org>, <rth at redhat dot com>
On Tue, 19 Jun 2001, Andrew Haley wrote:
> Also, I've written a MD_FALLBACK_FRAME_STATE_FOR for Linux. This
What is a MD_FALLBACK_FRAME_STATE_FOR? This doesn't seem to be mentioned
in the manual. Can someone please add documentation for this macro? Why
was documentation not added along with the code that added the use of the
macro? OK to commit the following patch to contribute.html to clarify the
requirement for documentation in such cases?
Index: contribute.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.33
diff -u -r1.33 contribute.html
--- contribute.html 2001/05/21 02:07:54 1.33
+++ contribute.html 2001/06/19 22:44:48
@@ -53,7 +53,9 @@
also add documentation for that option to the GCC manual.
Similarly, if it changes the behavior of an existing command
line option or other documented behavior, the patch must update
- the documentation.</li>
+ the documentation. Documentation is also required for any
+ changes or additions to the parts of the front-end and back-end
+ interfaces documented in the manual (such as new target macros).</li>
<li> It is strongly recommended the patch should add testcases for
any new features added and any bugs fixed to the testsuite, if
not already there. (You will of course have tested any new
--
Joseph S. Myers
jsm28@cam.ac.uk