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 r13-4411] fix Clang warning Date: Wed, 30 Nov 2022 13:48:07 +0000 (GMT) [thread overview] Message-ID: <20221130134807.0FB05385B1B3@sourceware.org> (raw) https://gcc.gnu.org/g:e2e272ba76b3bfda4a04b0c89ba984f6f6f2d7ea commit r13-4411-ge2e272ba76b3bfda4a04b0c89ba984f6f6f2d7ea Author: Martin Liska <mliska@suse.cz> Date: Wed Nov 30 14:47:03 2022 +0100 fix Clang warning Fixes: gcc/fortran/parse.cc:5782:32: warning: for loop has empty body [-Wempty-body] gcc/fortran/ChangeLog: * parse.cc (parse_omp_structured_block): Remove extra semicolon. Diff: --- gcc/fortran/parse.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/fortran/parse.cc b/gcc/fortran/parse.cc index 51ff0fc6ace..cdae43fa1fd 100644 --- a/gcc/fortran/parse.cc +++ b/gcc/fortran/parse.cc @@ -5779,7 +5779,7 @@ parse_omp_structured_block (gfc_statement omp_st, bool workshare_stmts_only) { gfc_omp_namelist *nl; for (nl = cp->ext.omp_clauses->lists[OMP_LIST_COPYPRIVATE]; - nl->next; nl = nl->next); + nl->next; nl = nl->next) ; nl->next = new_st.ext.omp_clauses->lists[OMP_LIST_COPYPRIVATE]; }
reply other threads:[~2022-11-30 13:48 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=20221130134807.0FB05385B1B3@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).