From f938987f60e922ee81a8fee9b14217d7a1b27c81 Mon Sep 17 00:00:00 2001 From: Hans-Peter Nilsson Date: Mon, 11 Jun 2012 22:46:45 +0000 Subject: [PATCH] tm.texi.in (Addressing Modes): Mention that this hook needs to be defined for native TLS. * doc/tm.texi.in (Addressing Modes) : Mention that this hook needs to be defined for native TLS. * doc/tm.texi: Regenerate. From-SVN: r188404 --- gcc/ChangeLog | 6 ++++++ gcc/doc/tm.texi | 6 ++++-- gcc/doc/tm.texi.in | 6 ++++-- 3 files changed, 14 insertions(+), 4 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index f39f91a1cd7..176e62141b5 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,9 @@ +2012-06-12 Hans-Peter Nilsson + + * doc/tm.texi.in (Addressing Modes) : + Mention that this hook needs to be defined for native TLS. + * doc/tm.texi: Regenerate. + 2012-06-11 Mike Stump * emit-rtl.c (init_emit_once): Iterate through the diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index aeccc79f39f..0715531af57 100644 --- 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 79b9e6eabef..00f288b6a16 100644 --- 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. -- 2.30.2