public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-1276] Fix "tailing" typo. Date: Tue, 8 Jun 2021 07:43:53 +0000 (GMT) [thread overview] Message-ID: <20210608074353.F0FC63947429@sourceware.org> (raw) https://gcc.gnu.org/g:48aa5c60034736a439f2214dac34b165e74a7d20 commit r12-1276-g48aa5c60034736a439f2214dac34b165e74a7d20 Author: Martin Liska <mliska@suse.cz> Date: Tue Jun 8 09:42:18 2021 +0200 Fix "tailing" typo. gcc/fortran/ChangeLog: * intrinsic.texi: Fix typo. * trans-expr.c (gfc_trans_pointer_assignment): Likewise. gcc/ChangeLog: * genautomata.c (create_automata): Fix typo. libgfortran/ChangeLog: * intrinsics/chmod.c (chmod_internal): Fix typo. * io/transfer.c (read_sf): Likewise. libquadmath/ChangeLog: * libquadmath.texi: Fix typo. gcc/testsuite/ChangeLog: * gcc.dg/format/strfmon-1.c: Fix typo. * gfortran.dg/char4-subscript.f90: Likewise. Diff: --- gcc/fortran/intrinsic.texi | 2 +- gcc/fortran/trans-expr.c | 2 +- gcc/genautomata.c | 2 +- gcc/testsuite/gcc.dg/format/strfmon-1.c | 2 +- gcc/testsuite/gfortran.dg/char4-subscript.f90 | 2 +- libgfortran/intrinsics/chmod.c | 2 +- libgfortran/io/transfer.c | 2 +- libquadmath/libquadmath.texi | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi index c9049b539d5..260dbaae76b 100644 --- a/gcc/fortran/intrinsic.texi +++ b/gcc/fortran/intrinsic.texi @@ -502,7 +502,7 @@ Inquiry function @item @emph{Arguments}: @multitable @columnfractions .15 .70 @item @var{NAME} @tab Scalar @code{CHARACTER} of default kind with the -file name. Tailing blank are ignored unless the character @code{achar(0)} +file name. Trailing blank are ignored unless the character @code{achar(0)} is present, then all characters up to and excluding @code{achar(0)} are used as file name. @item @var{MODE} @tab Scalar @code{CHARACTER} of default kind with the diff --git a/gcc/fortran/trans-expr.c b/gcc/fortran/trans-expr.c index e3bc8863f1b..de406ad2e8f 100644 --- a/gcc/fortran/trans-expr.c +++ b/gcc/fortran/trans-expr.c @@ -9513,7 +9513,7 @@ gfc_trans_pointer_assignment (gfc_expr * expr1, gfc_expr * expr2) { gfc_add_data_component (expr2); /* The following is required as gfc_add_data_component doesn't - update ts.type if there is a tailing REF_ARRAY. */ + update ts.type if there is a trailing REF_ARRAY. */ expr2->ts.type = BT_DERIVED; } diff --git a/gcc/genautomata.c b/gcc/genautomata.c index e6295e60757..6bbfc684afa 100644 --- a/gcc/genautomata.c +++ b/gcc/genautomata.c @@ -6787,7 +6787,7 @@ create_automata (void) finish_regexp_representation calls. */ /* This recursive function forms string representation of regexp - (without tailing '\0'). */ + (without trailing '\0'). */ static void form_regexp (regexp_t regexp) { diff --git a/gcc/testsuite/gcc.dg/format/strfmon-1.c b/gcc/testsuite/gcc.dg/format/strfmon-1.c index 934242a238c..a790db53c9d 100644 --- a/gcc/testsuite/gcc.dg/format/strfmon-1.c +++ b/gcc/testsuite/gcc.dg/format/strfmon-1.c @@ -57,7 +57,7 @@ foo (char *s, size_t m, double d, long double ld) strfmon (s, m, "%n%n", d); /* { dg-warning "matching" "too few args" } */ strfmon (s, m, ""); /* { dg-warning "zero-length" "empty" } */ strfmon (s, m, NULL); /* { dg-warning "null" "null format string" } */ - strfmon (s, m, "%"); /* { dg-warning "trailing" "tailing %" } */ + strfmon (s, m, "%"); /* { dg-warning "trailing" "trailing %" } */ strfmon (s, m, "%n\0", d); /* { dg-warning "embedded" "embedded NUL" } */ strfmon (s, m, "%^^n", d); /* { dg-warning "repeated" "repeated flag" } */ } diff --git a/gcc/testsuite/gfortran.dg/char4-subscript.f90 b/gcc/testsuite/gfortran.dg/char4-subscript.f90 index fd1cf69754e..b4e2d11d6c5 100644 --- a/gcc/testsuite/gfortran.dg/char4-subscript.f90 +++ b/gcc/testsuite/gfortran.dg/char4-subscript.f90 @@ -22,7 +22,7 @@ if (ichar(var%str2(5:5)) /= int(Z'1F608')) stop 2 deallocate(var%str2) end -! Note: the last '\x00' is regarded as string terminator, hence, the tailing \0 byte is not in the dump +! Note: the last '\x00' is regarded as string terminator, hence, the trailing \0 byte is not in the dump ! { dg-final { scan-tree-dump { \(\*var\.str2\)\[1\]{lb: 1 sz: 4} = "(d\\x00\\x00|\\x00\\x00\\x00d)"\[1\]{lb: 1 sz: 4};} "original" } } ! { dg-final { scan-tree-dump { __builtin_memmove \(\(void \*\) &\(\*var.str2\)\[2\]{lb: 1 sz: 4}, \(void \*\) &"(e\\x00\\x00\\x00f\\x00\\x00|\\x00\\x00\\x00e\\x00\\x00\\x00f)"\[1\]{lb: 1 sz: 4}, 8\);} "original" } } diff --git a/libgfortran/intrinsics/chmod.c b/libgfortran/intrinsics/chmod.c index d0371ce560f..f4057cb7d06 100644 --- a/libgfortran/intrinsics/chmod.c +++ b/libgfortran/intrinsics/chmod.c @@ -271,7 +271,7 @@ chmod_internal (char *file, char *mode, gfc_charlen_type mode_len) part = 3; break; - /* Tailing blanks are valid in Fortran. */ + /* Trailing blanks are valid in Fortran. */ case ' ': for (i++; i < mode_len; i++) if (mode[i] != ' ') diff --git a/libgfortran/io/transfer.c b/libgfortran/io/transfer.c index 36e35b48cd3..e44b2df6058 100644 --- a/libgfortran/io/transfer.c +++ b/libgfortran/io/transfer.c @@ -491,7 +491,7 @@ read_sf (st_parameter_dt *dtp, size_t *length) If the read is short, then it is because the current record does not have enough data to satisfy the read request and the file was - opened with PAD=YES. The caller must assume tailing spaces for + opened with PAD=YES. The caller must assume trailing spaces for short reads. */ void * diff --git a/libquadmath/libquadmath.texi b/libquadmath/libquadmath.texi index f9a44acef2b..261655950e4 100644 --- a/libquadmath/libquadmath.texi +++ b/libquadmath/libquadmath.texi @@ -309,7 +309,7 @@ the format. @item @emph{Arguments}: @multitable @columnfractions .15 .70 @item @var{s} @tab output string -@item @var{size} @tab byte size of the string, including tailing NUL +@item @var{size} @tab byte size of the string, including trailing NUL @item @var{format} @tab conversion specifier string @end multitable
reply other threads:[~2021-06-08 7:43 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210608074353.F0FC63947429@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).