[gcc r13-1023] doc: Fix up -Waddress documentation

[Jakub Jelinek <jakub@gcc.gnu.org>]

https://gcc.gnu.org/g:2dc19a1b590b9afb58fd5f779e87ae8fc1998ae7

commit r13-1023-g2dc19a1b590b9afb58fd5f779e87ae8fc1998ae7
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Jun 9 10:19:53 2022 +0200

    doc: Fix up -Waddress documentation
    
    WHen looking up the -Waddress documentation due to some PR that mentioned it,
    I've noticed some typos and thus I'm fixing them.
    
    2022-06-09  Jakub Jelinek  <jakub@redhat.com>
    
            * doc/invoke.texi (-Waddress): Fix a typo in small example.
            Fix typos inptr_t -> intptr_t and uinptr_t -> uintptr_t.

Diff:
---
 gcc/doc/invoke.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index ac0c06cd2b0..174bc09e5cf 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -8901,7 +8901,7 @@ such as in
 void f (void);
 void g (void)
 @{
-  if (!func)   // warning: expression evaluates to false
+  if (!f)   // warning: expression evaluates to false
     abort ();
 @}
 @end smallexample
@@ -8927,7 +8927,7 @@ weak symbols), so their use in a conditional might indicate missing
 parentheses in a function call or a missing dereference in an array
 expression.  The subset of the warning for object pointers can be
 suppressed by casting the pointer operand to an integer type such
-as @code{inptr_t} or @code{uinptr_t}.
+as @code{intptr_t} or @code{uintptr_t}.
 Comparisons against string literals result in unspecified behavior
 and are not portable, and suggest the intent was to call @code{strcmp}.
 The warning is suppressed if the suspicious expression is the result