public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102854] [OpenMP] Bogus "initializer expression refers to iteration variable" when using templates Date: Fri, 21 Jul 2023 10:34:37 +0000 [thread overview] Message-ID: <bug-102854-4-WLd8qlTRjG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102854-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102854 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> --- Close as FIXED - based on * my previous comment (comment 4) * based on the following: (In reply to Jakub Jelinek from comment #2) > WIP patch. Clearly still more work is needed, apparently pointer iterators > in non-rectangular loops are rejected, like: (example that is committed as part of PR106449) > and enabling it result in ICEs during omp-expand.c. Furthermore, for both > pointer and random access iterator non-rect loops, I think we cannot really use non-rectangular loops with random-access iterators. It works fine as long as the outer and the inner loop access different variables, an example for this is libgomp.c++/collapse-2.C → https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libgomp/testsuite/libgomp.c++/collapse-2.C;hb=HEAD But I currently see no way to use in the outer loop * a C++ iterator * a range-based for loop * a C-style index-variable loop and then to use 'outer' in any way, except of having yet another classic C-style loop. Everything else I came up ends up using an expression involving the outer iteration variable and not the bare variable. But that's rejected ("expression refers to iteration variable" error). > I should verify we only > allow the var-outer, var-outer + a2, a2 + var-outer and var-outer - a2 forms > and no others and test code generation. I believe that's what r12-4733-g2084b5f42a4432da8b0625f9c669bf690ec46468 does in c-c++-common/gomp/loop-9.c → https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/testsuite/c-c++-common/gomp/loop-9.c;hb=HEAD (Admittedly only for "initializer expression" and not for "condition expression" or "increment expression", but I can confirm that at last the condition error works.)
prev parent reply other threads:[~2023-07-21 10:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-20 9:43 [Bug c++/102854] New: " burnus at gcc dot gnu.org 2021-10-20 11:40 ` [Bug c++/102854] " burnus at gcc dot gnu.org 2021-10-21 16:42 ` jakub at gcc dot gnu.org 2021-10-27 7:28 ` cvs-commit at gcc dot gnu.org 2023-07-14 15:29 ` burnus at gcc dot gnu.org 2023-07-21 10:34 ` burnus 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-102854-4-WLd8qlTRjG@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).