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 c++/106829] [12/13 Regression] OpenMP offload internal compiler error: in gimplify_expr, at gimplify.cc:16222 since r12-5835 Date: Mon, 05 Sep 2022 10:51:17 +0000 [thread overview] Message-ID: <bug-106829-4-aexNQCk3Q4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106829-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106829 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|OpenMP offload internal |[12/13 Regression] OpenMP |compiler error: in |offload internal compiler |gimplify_expr, at |error: in gimplify_expr, at |gimplify.cc:16222 |gimplify.cc:16222 since | |r12-5835 Ever confirmed|0 |1 CC| |cltang at gcc dot gnu.org Target Milestone|--- |12.3 Status|UNCONFIRMED |NEW Priority|P3 |P2 Last reconfirmed| |2022-09-05 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with r12-5835-g0ab29cf0bb68960c1f87 Reduced testcase: template <typename> class complex; template <> struct complex<double> { complex(double); _Complex double d; }; struct S { void static foo (); }; void S::foo () { #pragma omp target complex<double> c = 0.0; }
next prev parent reply other threads:[~2022-09-05 10:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-05 5:03 [Bug c++/106829] New: OpenMP offload internal compiler error: in gimplify_expr, at gimplify.cc:16222 xw111luoye at gmail dot com 2022-09-05 10:14 ` [Bug c++/106829] " jakub at gcc dot gnu.org 2022-09-05 10:51 ` jakub at gcc dot gnu.org [this message] 2022-09-06 13:29 ` [Bug c++/106829] [12/13 Regression] OpenMP offload internal compiler error: in gimplify_expr, at gimplify.cc:16222 since r12-5835 jakub at gcc dot gnu.org 2022-09-07 6:57 ` cvs-commit at gcc dot gnu.org 2022-09-07 19:18 ` xw111luoye at gmail dot com 2022-11-03 0:22 ` cvs-commit 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-106829-4-aexNQCk3Q4@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).