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/108545] [13 Regression] ICE in install_var_field, at omp-low.cc:799 since r13-2665-g23baa717c991d77f Date: Tue, 28 Feb 2023 11:24:59 +0000 [thread overview] Message-ID: <bug-108545-4-9WWqvGRGM1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108545-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108545 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |burnus at gcc dot gnu.org --- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> --- Created attachment 54554 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54554&action=edit Draft patch - adds and uses tree_operand_sideeff_hash The patch does what I wrote last: Adds The problem (for the Fortran testcase but probably for both) occurs for omp_mapped_by_containing_struct's omp_mapping_group **wholestruct = grpmap->get (wsdecl); where 'wsdecl' is 'x.a'. If I look at operand_equal_p – invoked by 'tree_operand_hash::equal, I get 'true' without 'volatile' and 'false' with. The only difference is "side-effects volatile" for the component_ref and that "component_ref 0x7ffff6e25e70" are not identical but different tree; the arguments etc. are identical. In operand_compare::operand_equal_p there is: if (arg0 == arg1 && ! (flags & OEP_ONLY_CONST) && (TREE_CODE (arg0) == SAVE_EXPR || (flags & OEP_MATCH_SIDE_EFFECTS) || (! TREE_SIDE_EFFECTS (arg0) && ! TREE_SIDE_EFFECTS (arg1)))) return true; Thus, it seems as if we need a variant of gcc/tree-hash-traits.h that passes not 0 but OEP_MATCH_SIDE_EFFECTS as flag to operand_equal_p.
next prev parent reply other threads:[~2023-02-28 11:25 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-25 17:50 [Bug fortran/108545] New: [13 Regression] ICE in install_var_field, at omp-low.cc:799 gscfq@t-online.de 2023-01-26 7:44 ` [Bug fortran/108545] " rguenth at gcc dot gnu.org 2023-01-26 9:41 ` [Bug fortran/108545] [13 Regression] ICE in install_var_field, at omp-low.cc:799 since r13-2665-g23baa717c991d77f marxin at gcc dot gnu.org 2023-02-21 12:57 ` [Bug middle-end/108545] " rguenth at gcc dot gnu.org 2023-02-24 14:19 ` burnus at gcc dot gnu.org 2023-02-24 14:46 ` burnus at gcc dot gnu.org 2023-02-24 15:53 ` burnus at gcc dot gnu.org 2023-02-28 11:24 ` burnus at gcc dot gnu.org [this message] 2023-03-01 14:24 ` cvs-commit at gcc dot gnu.org 2023-03-01 14:28 ` 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-108545-4-9WWqvGRGM1@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).