public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95197] libgomp/testsuite/libgomp.c++/for-27.C fails with -std=c++17 Date: Sun, 14 Jun 2020 10:07:26 +0000 [thread overview] Message-ID: <bug-95197-4-djSEQ2fmBU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95197-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95197 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:6d6df84dc031924cb95599a6c498aa27d3bceac4 commit r10-8294-g6d6df84dc031924cb95599a6c498aa27d3bceac4 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue May 26 09:35:21 2020 +0200 openmp: Ensure copy ctor for composite distribute parallel for class iterators is instantiated [PR95197] During gimplification omp_finish_clause langhook is called in several places to add the language specific info to the clause like what default/copy ctors, dtors and assignment operators should be used. Unfortunately, if it refers to some not yet instantiated method, during gimplification it is too late and the methods will not be instantiated anymore. For other cases, the genericizer has code to detect those and instantiate whatever is needed, this change adds the same for distribute parallel for class iterators where we under the hood need a copy constructor for the iterator to implement it. 2020-05-26 Jakub Jelinek <jakub@redhat.com> PR c++/95197 * gimplify.c (find_combined_omp_for): Move to omp-general.c. * omp-general.h (find_combined_omp_for): Declare. * omp-general.c: Include tree-iterator.h. (find_combined_omp_for): New function, moved from gimplify.c. * cp-gimplify.c: Include omp-general.h. (cp_genericize_r) <case OMP_DISTRIBUTE>: For class iteration variables in composite distribute parallel for, instantiate copy ctor of their types. (cherry picked from commit f1f862aec2c3b93dbd6adfc35b0e1b6034e59c21)
prev parent reply other threads:[~2020-06-14 10:07 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-19 0:14 [Bug c++/95197] New: " mpolacek at gcc dot gnu.org 2020-05-25 14:23 ` [Bug c++/95197] " jakub at gcc dot gnu.org 2020-05-25 14:38 ` jakub at gcc dot gnu.org 2020-05-25 16:55 ` jakub at gcc dot gnu.org 2020-05-26 7:39 ` cvs-commit at gcc dot gnu.org 2020-06-14 10:07 ` cvs-commit 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-95197-4-djSEQ2fmBU@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).