public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: Tobias Burnus <tobias@codesourcery.com>
Subject: [PATCH (pushed)] fix Clang warning
Date: Wed, 30 Nov 2022 14:47:39 +0100	[thread overview]
Message-ID: <13330943-7eca-20ac-b6e9-2c61d6aaf048@suse.cz> (raw)

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.
---
 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];
 	}
-- 
2.38.1


                 reply	other threads:[~2022-11-30 13:47 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=13330943-7eca-20ac-b6e9-2c61d6aaf048@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tobias@codesourcery.com \
    /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: link
Be 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).