public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kwok Yeung <kcy@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/omp/gcc-12] Fix tree check failure with reduction localization Date: Wed, 29 Jun 2022 14:36:12 +0000 (GMT) [thread overview] Message-ID: <20220629143612.634A638485A2@sourceware.org> (raw) https://gcc.gnu.org/g:9793ca937c6c88b944870259c87b934cf9747d0b commit 9793ca937c6c88b944870259c87b934cf9747d0b Author: Julian Brown <julian@codesourcery.com> Date: Fri Sep 6 04:42:16 2019 -0700 Fix tree check failure with reduction localization gcc/ * gimplify.cc (gimplify_omp_workshare): Use OMP_CLAUSES, OMP_BODY instead of OMP_TARGET_CLAUSES, OMP_TARGET_BODY. Diff: --- gcc/ChangeLog.omp | 5 +++++ gcc/gimplify.cc | 3 +-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/gcc/ChangeLog.omp b/gcc/ChangeLog.omp index de0cdc40fbd..ac314abcc14 100644 --- a/gcc/ChangeLog.omp +++ b/gcc/ChangeLog.omp @@ -1,3 +1,8 @@ +2019-09-06 Julian Brown <julian@codesourcery.com> + + * gimplify.cc (gimplify_omp_workshare): Use OMP_CLAUSES, OMP_BODY + instead of OMP_TARGET_CLAUSES, OMP_TARGET_BODY. + 2019-09-05 Cesar Philippidis <cesar@codesourcery.com> Julian Brown <julian@codesourcery.com> diff --git a/gcc/gimplify.cc b/gcc/gimplify.cc index 585abe0667c..5d0a51438ac 100644 --- a/gcc/gimplify.cc +++ b/gcc/gimplify.cc @@ -14456,8 +14456,7 @@ gimplify_omp_workshare (tree *expr_p, gimple_seq *pre_p) /* FIXME: Reductions are not supported in kernels regions yet. */ if (/*ort == ORT_ACC_KERNELS ||*/ ort == ORT_ACC_PARALLEL) - localize_reductions (OMP_TARGET_CLAUSES (*expr_p), - OMP_TARGET_BODY (*expr_p)); + localize_reductions (OMP_CLAUSES (expr), OMP_BODY (expr)); gimple *g = gimplify_and_return_first (OMP_BODY (expr), &body); if (gimple_code (g) == GIMPLE_BIND)
reply other threads:[~2022-06-29 14:36 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=20220629143612.634A638485A2@sourceware.org \ --to=kcy@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).