This documents some constraints on TYPE_ADDR_SPACE in tcc_reference
trees.
Documentation around types seems to be mostly non-existient ... but
since I opened this bug I might as well try to fix it (minimally).
OK?
PR middle-end/113762
* generic.texi (Types): Document TYPE_ADDR_SPACE.
(Storage References): Document where to get at the address-space
accessed.
---
gcc/doc/generic.texi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/gcc/doc/generic.texi b/gcc/doc/generic.texi
index d4ac580a7a8..f0ed2698b67 100644
--- a/gcc/doc/generic.texi
+++ b/gcc/doc/generic.texi
@@ -345,6 +345,9 @@ The following functions and macros deal with
cv-qualification of types:
This macro returns the unqualified version of a type. It may be applied
to an unqualified type, but it is not always the identity function in
that case.
+
+@item TYPE_ADDR_SPACE
+This macro returns the address space objects of this type reside in.
@end ftable
A few other macros and functions are usable with all types:
@@ -1290,6 +1293,11 @@ The type of the node specifies the alignment of the
access.
@end table
+The referenced address-space is available as @code{TYPE_ADDR_SPACE}
+of the reference type and should be consistent along the types of a
+reference composed of nested storage reference trees.
+
+
@node Unary and Binary Expressions
@subsection Unary and Binary Expressions
@tindex NEGATE_EXPR
--
2.43.0