Include the term used in the standard to ease further research for users.
gcc/ChangeLog:
* doc/invoke.texi: Use "compatible types" term.
---
gcc/doc/invoke.texi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index b3f7f0479cc4..ad749f2fd258 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -14552,10 +14552,10 @@ Allow the compiler to assume the strictest aliasing
rules applicable to
the language being compiled. For C (and C++), this activates
optimizations based on the type of expressions. In particular, an
object of one type is assumed never to reside at the same address as an
-object of a different type, unless the types are almost the same. For
-example, an @code{unsigned int} can alias an @code{int}, but not a
-@code{void*} or a @code{double}. A character type may alias any other
-type.
+object of a different type, unless the types are almost the same
+(``compatible types''). For example, an @code{unsigned int} can alias an
+@code{int}, but not a @code{void*} or a @code{double}. A character type may
+alias any other type.
@anchor{Type-punning}Pay special attention to code like this:
@smallexample
base-commit: 2e7c1b589bc58be0e155098cf87d8535d41adeab
--
2.49.0
