From: Julian Brown <julian@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <fortran@gcc.gnu.org>, Tobias Burnus <tobias@codesourcery.com>,
<jakub@redhat.com>
Subject: [PATCH 1/7] Fix up merge/formatting errors
Date: Fri, 30 Jun 2023 19:23:28 +0000 [thread overview]
Message-ID: <f55d42cc902dfba9a0ae5fd5f670c535afb3f24e.1688151381.git.julian@codesourcery.com> (raw)
In-Reply-To: <cover.1688151381.git.julian@codesourcery.com>
This patch fixes a couple of minor merge/formatting errors.
2023-06-30 Julian Brown <julian@codesourcery.com>
gcc/fortran/
* parse.cc (decode_omp_directive): Add missing break.
gcc/
* gimplify.cc (gimplify_adjust_omp_clauses): Fix indentation.
---
gcc/fortran/parse.cc | 1 +
gcc/gimplify.cc | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/gcc/fortran/parse.cc b/gcc/fortran/parse.cc
index 73f15608260..2467adf5836 100644
--- a/gcc/fortran/parse.cc
+++ b/gcc/fortran/parse.cc
@@ -902,6 +902,7 @@ decode_omp_directive (void)
break;
case 't':
matchs ("tile sizes", gfc_match_omp_tile, ST_OMP_TILE);
+ break;
case 'u':
matchs ("unroll", gfc_match_omp_unroll, ST_OMP_UNROLL);
break;
diff --git a/gcc/gimplify.cc b/gcc/gimplify.cc
index 1e90d2ed031..707a0c046de 100644
--- a/gcc/gimplify.cc
+++ b/gcc/gimplify.cc
@@ -13996,8 +13996,8 @@ gimplify_adjust_omp_clauses (gimple_seq *pre_p, gimple_seq body, tree *list_p,
fb_lvalue) == GS_ERROR)
remove = true;
gimplify_omp_ctxp = ctx;
- break;
- }
+ break;
+ }
if ((code == OMP_TARGET
|| code == OMP_TARGET_DATA
--
2.25.1
next prev parent reply other threads:[~2023-06-30 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 19:23 [PATCH 0/7] [og13] OpenMP: lvalue parsing and "declare mapper" support Julian Brown
2023-06-30 19:23 ` Julian Brown [this message]
2023-06-30 19:23 ` [PATCH 2/7] OpenMP: OpenMP 5.2 semantics for pointers with unmapped target Julian Brown
2023-06-30 19:23 ` [PATCH 3/7] OpenMP: lvalue parsing for map/to/from clauses (C++) Julian Brown
2023-06-30 19:23 ` [PATCH 4/7] OpenMP: C++ "declare mapper" support Julian Brown
2023-06-30 19:23 ` [PATCH 5/7] OpenMP: lvalue parsing for map clauses (C) Julian Brown
2023-06-30 19:23 ` [PATCH 6/7] OpenMP: Support OpenMP 5.0 "declare mapper" directives for C Julian Brown
2023-06-30 19:23 ` [PATCH 7/7] OpenMP: Fortran "!$omp declare mapper" support Julian Brown
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=f55d42cc902dfba9a0ae5fd5f670c535afb3f24e.1688151381.git.julian@codesourcery.com \
--to=julian@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).