https://gcc.gnu.org/g:9933a963a587349e22862668ea693bc1d4cc6693

commit r15-9737-g9933a963a587349e22862668ea693bc1d4cc6693
Author: Jonathan Wakely <jwak...@redhat.com>
Date:   Tue May 27 09:11:58 2025 +0100

    doc: Fix typo in description of nonstring attribute
    
    gcc/ChangeLog:
    
            * doc/extend.texi (Common Variable Attributes): Fix typo in
            description of nonstring.
    
    (cherry picked from commit 351e60095cfaa73b5ac69222d00e0cd4ae5725d4)

Diff:
---
 gcc/doc/extend.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 0978c4c41b25..72b8e3720a3d 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -7336,7 +7336,7 @@ truncate the copy without appending the terminating 
@code{NUL} character.
 Using the attribute makes it possible to suppress the warning.  However,
 when the array is declared with the attribute the call to @code{strlen} is
 diagnosed because when the array doesn't contain a @code{NUL}-terminated
-string the call is undefined.  To copy, compare, of search non-string
+string the call is undefined.  To copy, compare, or search non-string
 character arrays use the @code{memcpy}, @code{memcmp}, @code{memchr},
 and other functions that operate on arrays of bytes.  In addition,
 calling @code{strnlen} and @code{strndup} with such arrays is safe

Reply via email to