From: Jakub Jelinek <jakub@redhat.com>
To: Kwok Cheung Yeung <kcy@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 4/7] openmp: Add support for streaming metadirectives and resolving them after LTO
Date: Mon, 30 May 2022 13:33:54 +0200 [thread overview]
Message-ID: <YpSroi6oPlx20WnM@tucnak> (raw)
In-Reply-To: <0813fb26-b6ec-0a39-11aa-4a4687947531@codesourcery.com>
On Fri, Dec 10, 2021 at 05:36:20PM +0000, Kwok Cheung Yeung wrote:
> 2021-12-10 Kwok Cheung Yeung <kcy@codesourcery.com>
>
> gcc/
> * Makefile.in (OBJS): Add omp-expand-metadirective.o.
> * gimple-streamer-in.c (input_gimple_stmt): Add case for
> GIMPLE_OMP_METADIRECTIVE. Handle metadirective labels.
> * gimple-streamer-out.c (output_gimple_stmt): Likewise.
> * omp-expand-metadirective.cc: New.
> * passes.def: Add pass_omp_expand_metadirective.
> * tree-pass.h (make_pass_omp_expand_metadirective): New prototype.
> ---
> gcc/Makefile.in | 1 +
> gcc/gimple-streamer-in.c | 10 ++
> gcc/gimple-streamer-out.c | 6 +
> gcc/omp-expand-metadirective.cc | 191 ++++++++++++++++++++++++++++++++
> gcc/passes.def | 1 +
> gcc/tree-pass.h | 1 +
> 6 files changed, 210 insertions(+)
> create mode 100644 gcc/omp-expand-metadirective.cc
>
> @@ -151,6 +151,7 @@ input_gimple_stmt (class lto_input_block *ib, class data_in *data_in,
> case GIMPLE_COND:
> case GIMPLE_GOTO:
> case GIMPLE_DEBUG:
> + case GIMPLE_OMP_METADIRECTIVE:
> for (i = 0; i < num_ops; i++)
> {
> tree *opp, op = stream_read_tree (ib, data_in);
> @@ -188,6 +189,15 @@ input_gimple_stmt (class lto_input_block *ib, class data_in *data_in,
> else
> gimple_call_set_fntype (call_stmt, stream_read_tree (ib, data_in));
> }
> + if (gomp_metadirective *metadirective_stmt
> + = dyn_cast <gomp_metadirective*> (stmt))
> + {
> + gimple_alloc_omp_metadirective (metadirective_stmt);
> + for (i = 0; i < num_ops; i++)
> + gimple_omp_metadirective_set_label (metadirective_stmt, i,
> + stream_read_tree (ib,
> + data_in));
> + }
Ah, sorry for the comment about LTO streaming, here it is.
> --- /dev/null
> +++ b/gcc/omp-expand-metadirective.cc
> @@ -0,0 +1,191 @@
> +/* Expand an OpenMP metadirective.
> +
> + Copyright (C) 2021 Free Software Foundation, Inc.
We have 2022 now...
> +
Missing function comment.
> +static void
> +omp_expand_metadirective (function *fun, basic_block bb)
> +{
> + gimple *stmt = last_stmt (bb);
> + vec<struct omp_metadirective_variant> candidates
> + = omp_resolve_metadirective (stmt);
> +
> + /* This is the last chance for the metadirective to be resolved. */
> + if (candidates.is_empty ())
> + gcc_unreachable ();
gcc_assert (!candidates.is_empty ());
?
> + /* opt_pass methods: */
> + virtual bool gate (function *)
> + {
> + return (flag_openmp);
Useless ()s around it.
But much more importantly, I don't really like this to be a separate pass,
walking the whole IL once more is expensive, even when you restrict it
to just flag_openmp.
Late declare variant resolving is done in the (now a little bit misnamed)
pass_omp_device_lower.
The gate of that pass is right now:
return (!(fun->curr_properties & PROP_gimple_lomp_dev)
|| (flag_openmp
&& cgraph_node::get (fun->decl)->calls_declare_variant_alt));
so it would be nice to track (conservatively)
whether current function has any metadirectives
in it which aren't yet resolved (but perhaps the calls_declare_variant_alt
bit could be abused for that too) andin that case also deal with those.
You can surely gather them in the omp-offload.cc pass and then call
a function in your new file to handle that.
Jakub
next prev parent reply other threads:[~2022-05-30 11:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 11:16 [WIP, OpenMP] OpenMP metadirectives support Kwok Cheung Yeung
2021-07-26 11:38 ` Kwok Cheung Yeung
2021-07-26 14:29 ` Jakub Jelinek
2021-07-26 19:28 ` Kwok Cheung Yeung
2021-07-26 19:56 ` Jakub Jelinek
2021-07-26 21:19 ` Kwok Cheung Yeung
2021-07-26 21:23 ` Jakub Jelinek
2021-07-26 21:27 ` Kwok Cheung Yeung
2022-01-28 16:33 ` [PATCH] openmp: Add warning when functions containing metadirectives with 'construct={target}' called directly Kwok Cheung Yeung
2021-12-10 17:27 ` [WIP, OpenMP] OpenMP metadirectives support Kwok Cheung Yeung
2021-12-10 17:29 ` [PATCH 0/7] openmp: " Kwok Cheung Yeung
2021-12-10 17:31 ` [PATCH 1/7] openmp: Add C support for parsing metadirectives Kwok Cheung Yeung
2022-02-18 21:09 ` [PATCH] openmp: Improve handling of nested OpenMP metadirectives in C and C++ (was: Re: [PATCH 1/7] openmp: Add C support for parsing metadirectives) Kwok Cheung Yeung
2022-02-18 21:26 ` [og11][committed] openmp: Improve handling of nested OpenMP metadirectives in C and C++ Kwok Cheung Yeung
2022-05-27 17:44 ` [PATCH 1/7] openmp: Add C support for parsing metadirectives Jakub Jelinek
2021-12-10 17:33 ` [PATCH 2/7] openmp: Add middle-end support for metadirectives Kwok Cheung Yeung
2022-05-30 10:54 ` Jakub Jelinek
2021-12-10 17:35 ` [PATCH 3/7] openmp: Add support for resolving metadirectives during parsing and Gimplification Kwok Cheung Yeung
2022-05-30 11:13 ` Jakub Jelinek
2021-12-10 17:36 ` [PATCH 4/7] openmp: Add support for streaming metadirectives and resolving them after LTO Kwok Cheung Yeung
2022-05-30 11:33 ` Jakub Jelinek [this message]
2021-12-10 17:37 ` [PATCH 5/7] openmp: Add C++ support for parsing metadirectives Kwok Cheung Yeung
2022-05-30 11:52 ` Jakub Jelinek
2021-12-10 17:39 ` [PATCH 6/7] openmp, fortran: Add Fortran " Kwok Cheung Yeung
2022-02-14 15:09 ` Kwok Cheung Yeung
2022-02-14 15:17 ` Kwok Cheung Yeung
2021-12-10 17:40 ` [PATCH 7/7] openmp: Add testcases for metadirectives Kwok Cheung Yeung
2022-05-27 13:42 ` Jakub Jelinek
2022-01-24 21:28 ` [PATCH] openmp: Metadirective patch fixes Kwok Cheung Yeung
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=YpSroi6oPlx20WnM@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kcy@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).