diff mbox

[RFA:] doc: TARGET_LEGITIMIZE_ADDRESS needs to be defined for native TLS

Message ID 201205160024.q4G0O2aH018635@ignucius.se.axis.com
State New
Headers show

Commit Message

Hans-Peter Nilsson May 16, 2012, 12:24 a.m. UTC 
An old patch I finally came around to submit.
Verified that the DVI and info output looks ok.

Ok to commit with inherent relicensing and whatever?

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


brgds, H-P

Comments

Richard Henderson June 11, 2012, 9:23 p.m. UTC | #1 
On 2012-05-15 17:24, Hans-Peter Nilsson wrote:
> gcc:
> 	* doc/tm.texi.in (Addressing Modes) <TARGET_LEGITIMIZE_ADDRESS>:
> 	Mention that this hook needs to be defined for native TLS.
> 	* doc/tm.texi: Regenerate.

Ok.


r~
diff mbox

Patch

Index: doc/tm.texi.in
===================================================================
--- doc/tm.texi.in	(revision 187568)
+++ doc/tm.texi.in	(working copy)
@@ -5465,8 +5465,10 @@  The code of the hook should not alter th
 @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.