public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/108749] [OpenMP][C/C++/Fortran] inscan reduction modifier rejected for combined/composite constructs of simd/for/do Date: Fri, 10 Feb 2023 11:11:23 +0000 [thread overview] Message-ID: <bug-108749-4-XGs34VpN2b@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108749-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108749 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Perhaps it is implementable also for taskloop, but with a lot of work. The way how e.g. for/do works with inscan is that the two parts of the loop are split up, and one essentially gets two worksharing loops with the same number of iterations, one doing one part, then some single (or in parallel) middle-part and then another doing the other part. With tasks, perhaps we could create separate tasks for the two halves, spawn a taskloop that does one part, then a task that depends on all those tasks and does the merging in the middle and finally another taskloop that does the other part. But I think this is something that hasn't been even considered when just tweaking the wording. After all, if we want to allow inscan on taskloop simd and constructs combined with that, we'd first want to allow it on taskloop itself.
prev parent reply other threads:[~2023-02-10 11:11 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-10 10:11 [Bug other/108749] New: " burnus at gcc dot gnu.org 2023-02-10 10:18 ` [Bug other/108749] " jakub at gcc dot gnu.org 2023-02-10 10:27 ` jakub at gcc dot gnu.org 2023-02-10 11:00 ` burnus at gcc dot gnu.org 2023-02-10 11:11 ` jakub at gcc dot gnu.org [this message]
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=bug-108749-4-XGs34VpN2b@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).