Add support for target specific, language specific object files.

From-SVN: r37726

1 files changed, 12 insertions, 0 deletions

diff --git a/gcc/tm.texi b/gcc/tm.texi
index 4752d933dc6..cb923653c36 100644
--- a/gcc/tm.texi
+++ b/gcc/tm.texi
@@ -7905,6 +7905,18 @@ Note that both @var{space} and @var{name} are case sensitive.
 
 For an example use of this routine, see @file{c4x.h} and the callback
 routines defined in @file{c4x.c}.
+
+Note that the use of @code{c_lex} is specific to the C and C++
+compilers.  It will not work in the Java or Fortran compilers, or any
+other language compilers for that matter.  Thus if @code{c_lex} is going
+to be called from target-specific code, it must only be done so when
+building hte C and C++ compilers.  This can be done by defining the
+variables @code{c_target_objs} and @code{cxx_target_objs} in the
+target entry in the @code{config.gcc} file.  These variables should name
+the target-specific, language-specific object file which contains the
+code that uses @code{c_lex}.  Note it will also be necessary to add a
+rule to the makefile fragment pointed to by @code{tmake_file} that shows
+how to build this object file.
 @end deftypefun
 
 @deftypefun void cpp_register_pragma_space (cpp_reader *@var{pfile}, const char *@var{space})