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 middle-end/107028] [13 Regression][OpenACC] ICE in install_var_field, at omp-low.cc:797 Date: Sat, 24 Sep 2022 21:35:11 +0000 [thread overview] Message-ID: <bug-107028-4-qmNZjlsNSN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107028-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107028 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jules at gcc dot gnu.org --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> --- The problem is that for 8 | #pragma acc data copyin(a, a.data) the function install_var_field is called twice, both times with: install_var_field (var=0x7ffff6fd8d80, by_ref=true, mask=3, ctx=0x30abd50) where var is var_decl 'a'. This then runs into the assert: 797 gcc_assert ((mask & 1) == 0 798 || !splay_tree_lookup (ctx->field_map, key)); * * * BTW, in GCC 12 (and OG12), the omplower dump is: #pragma omp target oacc_data map(to:a [len: 4]) map(to:a.data [len: 4]) * * * Unless I messed up with bisecting, the culprit is r13-2665-g23baa717c991d77f206a9358ce2c04960ccf9eea OpenMP/OpenACC struct sibling list gimplification extension and rework
next prev parent reply other threads:[~2022-09-24 21:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-24 18:58 [Bug middle-end/107028] New: " burnus at gcc dot gnu.org 2022-09-24 21:35 ` burnus at gcc dot gnu.org [this message] 2022-09-25 5:51 ` [Bug middle-end/107028] " burnus at gcc dot gnu.org 2022-09-26 9:20 ` rguenth at gcc dot gnu.org 2022-09-29 14:05 ` cvs-commit at gcc dot gnu.org 2022-09-29 17:35 ` 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-107028-4-qmNZjlsNSN@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).