tm.texi.in (Addressing Modes): Mention that this hook needs to be defined for native...

	* doc/tm.texi.in (Addressing Modes) <TARGET_LEGITIMIZE_ADDRESS>:
	Mention that this hook needs to be defined for native TLS.
	* doc/tm.texi: Regenerate.

From-SVN: r188404

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index f39f91a1cd77f1a20e92f01c2ea3652a1e1278a6..176e62141b52799f4bbe3959e0d870ceb5dc1b03 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,9 @@
+2012-06-12  Hans-Peter Nilsson  <hp@axis.com>
+
+       * doc/tm.texi.in (Addressing Modes) <TARGET_LEGITIMIZE_ADDRESS>:
+       Mention that this hook needs to be defined for native TLS.
+       * doc/tm.texi: Regenerate.
+
 2012-06-11  Mike Stump  <mikestump@comcast.net>
 
        * emit-rtl.c (init_emit_once): Iterate through the

diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi
index aeccc79f39f936ea0c01ad2e88d65b4acc1eed2a..0715531af5728d42fb16a696a485b4111702478c 100644 (file)
--- a/gcc/doc/tm.texi
+++ b/gcc/doc/tm.texi
@@ -5529,8 +5529,10 @@ The code of the hook should not alter the substructure of
 @var{x}.  If it transforms @var{x} into a more legitimate form, it
 should return the new @var{x}.
 
-It is not necessary for this hook to come up with a legitimate address.
-The compiler has standard ways of doing so in all cases.  In fact, it
+It is not necessary for this hook to come up with a legitimate address,
+with the exception of native TLS addresses (@pxref{Emulated TLS}).
+The compiler has standard ways of doing so in all cases.  In fact, if
+the target supports only emulated TLS, it
 is safe to omit this hook or make it return @var{x} if it cannot find
 a valid way to legitimize the address.  But often a machine-dependent
 strategy can generate better code.

diff --git a/gcc/doc/tm.texi.in b/gcc/doc/tm.texi.in
index 79b9e6eabef7d94a8b523f315a01086c7aca3297..00f288b6a169897607d7df1aa04dfc6dcc0a59ea 100644 (file)
--- a/gcc/doc/tm.texi.in
+++ b/gcc/doc/tm.texi.in
@@ -5465,8 +5465,10 @@ The code of the hook should not alter the substructure of
 @var{x}.  If it transforms @var{x} into a more legitimate form, it
 should return the new @var{x}.
 
-It is not necessary for this hook to come up with a legitimate address.
-The compiler has standard ways of doing so in all cases.  In fact, it
+It is not necessary for this hook to come up with a legitimate address,
+with the exception of native TLS addresses (@pxref{Emulated TLS}).
+The compiler has standard ways of doing so in all cases.  In fact, if
+the target supports only emulated TLS, it
 is safe to omit this hook or make it return @var{x} if it cannot find
 a valid way to legitimize the address.  But often a machine-dependent
 strategy can generate better code.