Re: [patch 2/3] tm.texi documentation on macro PREFERRED_RENAME_CLASS

[Steve Ellcey <sje at cup dot hp dot com>]

| Please see what I said about putting the documentation in target.def.
| tm.texi.in should *only* have the @hook line and not the rest of the
| documentation.  Using "" for documentation in DEFHOOK in target.def is a
| deprecated transitional measure for cases where documentation uses
| pre-existing GFDL-only text, unless and until the FSF works out viable
| arrangements for us to be able to move and copy text bidirectionally
| between code and manuals in whatever ways make technical sense.
| 
| --
| Joseph S. Myers
| joseph@codesourcery.com

When adding a new hook with documentation in target.def, does tm.texi.in
need to be changed to add the @hook line?  In adding the new
TARGET_GET_RAW_RESULT_MODE and TARGET_GET_RAW_ARG_MODE hooks, it seems
that adding them (with the description) to target.def is enough to get
them into tm.texi without changing tm.texi.in.  Is the '@hook' in
tm.texi.in only needed if you want to control where the hooks are
documented or is putting @hook in tm.texi.in a requirement for all
hooks, even those documented in target.def?

Steve Ellcey
sje@cup.hp.com