diff mbox

RFA: hook signture patches (1/11): Introduction

Message ID 20100629215528.1j64f9w5k4kg4c0w-nzlynne@webmail.spamcop.net
State New
Headers show

Commit Message

Joern Rennecke June 30, 2010, 1:55 a.m. UTC 
As discussed recently on the gcc mailing list, we think we can move
function declarations between GPLed code and GFDLed documentation without
requiring special license grants and/or permission fom the FSF.

If there was a discagreement regarding the type between code and documentation,
I've adjusted the latter.  With regards to names, I generally used the
majority used name in the hook implementation code; for exp / expr,
I used the majority of code in trunk/gcc/*.c in general.

In general, in tm.texi, there is no blank line between the function
declaration and the documentation block; a number of the hooks converted
had an extra blank, line, which I removed for consistency.

Bootstrapped & regression testing on i686-pc-linux-gnu in revision 161563.

2010-06-29  Joern Rennecke  <joern.rennecke@embecosm.com>

	* target.def: Remove comment about licensing problems of function
	declaration.

Comments

Richard Henderson June 30, 2010, 4:11 p.m. UTC | #1 
All 11 patches are ok.


r~
diff mbox

Patch

Index: target.def
===================================================================
--- target.def	(revision 161563)
+++ target.def	(working copy)
@@ -63,8 +63,8 @@  HOOK_VECTOR (TARGET_INITIALIZER, gcc_tar
    the paragraph with @end deftypefn / deftypevr as appropriate, and marking
    the next autogenerated hook with @hook <hookname>.
    In both these cases, leave the DOC string empty, i.e. "".
-   Sometimes, the function declaration itself is only available under the
-   GPL, and/or for some historic reason it has to be documented differently
+   Sometimes, for some historic reason the function declaration 
+   has to be documented differently
    than what it is.  In that case, use DEFHOOK_UNDOC to supress auto-generation
    of documentation.  DEFHOOK_UNDOC takes a DOC string which it ignores, so
    you can put GPLed documentation string there if you have hopes that you