public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/102310] [11/12 Regression] ICE in visit_ref_for_mod_analysis with OpenACC Date: Fri, 08 Oct 2021 09:07:22 +0000 [thread overview] Message-ID: <bug-102310-4-twaC7D9hlZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102310-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102310 Martin Jambor <jamborm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamborm at gcc dot gnu.org --- Comment #6 from Martin Jambor <jamborm at gcc dot gnu.org> --- Both the ICE in visit_ref_for_mod_analysis and the ICE in expand_expr_real_1 happen when there the IL includes a PARM_DECL of a different function. So I suspect that OpenACC outlining or something carried over a PARM_DECL from one function to another, forgetting to properly copy it. In my experience, using dumps with UIDs (i.g. with -fdump-tree-all-uid) helps tremendously when debugging these.
next prev parent reply other threads:[~2021-10-08 9:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-13 17:06 [Bug middle-end/102310] New: " ygribov at gcc dot gnu.org 2021-09-14 6:54 ` [Bug ipa/102310] [11/12 Regression] " rguenth at gcc dot gnu.org 2021-09-14 7:19 ` marxin at gcc dot gnu.org 2021-09-14 7:35 ` tschwinge at gcc dot gnu.org 2021-09-14 8:48 ` tetra2005 at gmail dot com 2021-10-07 15:54 ` hubicka at gcc dot gnu.org 2021-10-08 9:07 ` jamborm at gcc dot gnu.org [this message] 2022-04-21 7:50 ` rguenth at gcc dot gnu.org 2022-09-23 15:23 ` [Bug ipa/102310] [11/12/13 " tschwinge at gcc dot gnu.org 2023-05-29 10:05 ` [Bug ipa/102310] [11/12/13/14 " jakub at gcc dot gnu.org 2024-04-30 13:04 ` [Bug ipa/102310] [11/12 " jamborm 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-102310-4-twaC7D9hlZ@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).