This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] Document TARGET_HAVE_TLS and TARGET_HAVE_SRODATA_SECTION


	I went back to document HAVE_SRODATA_SECTION and discovered that
HAVE_TLS is not documented either.  Do the descriptions below look
satisfactory?

David

	* doc/tm.texi (TARGET_HAVE_SRODATA_SECTION): Document.
	(TARGET_HAVE_TLS): Document.

Index: tm.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/doc/tm.texi,v
retrieving revision 1.164
diff -c -p -r1.164 tm.texi
*** tm.texi	7 Sep 2002 00:19:27 -0000	1.164
--- tm.texi	9 Sep 2002 18:44:16 -0000
*************** Returns true if @var{exp} should be plac
*** 5924,5929 ****
--- 5924,5934 ----
  The default version of this hook always returns false.
  @end deftypefn
  
+ @deftypevar {Target Hook} bool TARGET_HAVE_SRODATA_SECTION
+ Contains the value true if the target places read-only
+ ``small data'' into a separate section.  The default value is false.
+ @end deftypevar
+ 
  @deftypefn {Target Hook} bool TARGET_BINDS_LOCAL_P (tree @var{exp})
  Returns true if @var{exp} names an object for which name resolution
  rules must resolve to the current ``module'' (dynamic shared library
*************** The default version of this hook impleme
*** 5933,5938 ****
--- 5938,5949 ----
  for ELF, which has a looser model of global name binding than other
  currently supported object file formats.
  @end deftypefn
+ 
+ @deftypevar {Target Hook} bool TARGET_HAVE_TLS
+ Contains the value true if the target supports thread-local storage.
+ The default value is false.
+ @end deftypevar
+ 
  
  @node PIC
  @section Position Independent Code


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]