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, 14 Jul 2023 15:29:14 +0000 [thread overview] Message-ID: <bug-102854-4-qurCvaPRud@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 --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> --- The testcase of comment 2 seems to be the same as the one of bug 106449 comment 4, which went in as r13-1887-g97d32048c04e97 openmp: Fix up handling of non-rectangular simd loops with pointer type iterators [PR106449] A slightly modified variant of that testcase went in follow-up commit r13-1893-g85fe7e7dd1f146 Add libgomp.c-c++-common/pr106449-2.c * * * From the bug comments, it seems as if the following remains: "Non-rectangular loops with class random access iterators remain broken, that is something to be fixed incrementally." * * * However, given the commit for PR106449 (see above) and the earlier commit r12-4733-g2084b5f42a4432 openmp: Allow non-rectangular loops with pointer iterators (committed right after the commit of comment 3): I wonder whether the only thing that remains to be done is to add a real C++ testcase for random access iterator non-rect loops - assuming that the pointer patches cover all what's needed in terms of compiler support.
next prev parent reply other threads:[~2023-07-14 15:29 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 [this message] 2023-07-21 10:34 ` burnus at gcc dot gnu.org
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-qurCvaPRud@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).