public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107029] New: ice during GIMPLE pass: reassoc Date: Sat, 24 Sep 2022 19:34:50 +0000 [thread overview] Message-ID: <bug-107029-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107029 Bug ID: 107029 Summary: ice during GIMPLE pass: reassoc Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- This C++ code: class ImplicitBool ImplicitBool::*Reset___trans_tmp_1; int ImplicitBool::*Reset___trans_tmp_2; struct Chips { struct Clocks { void Reset(bool, bool); int next; }; void Reset(); Clocks clocks; }; void Chips::Clocks::Reset(bool mmc5Chip, bool fdsChip) { next = mmc5Chip || fdsChip; } void Chips::Reset() { clocks.Reset(Reset___trans_tmp_1, Reset___trans_tmp_2); } when compiled as follows by recent g++ $ ../results/bin/g++ -c -w -O2 -std=c++98 bug849.cc does this: bug849.cc: In member function ‘void Chips::Reset()’: bug849.cc:14:6: error: invalid types for ‘bit_and_expr’ 14 | void Chips::Reset() { clocks.Reset(Reset___trans_tmp_1, Reset___trans_tmp_2); } | ^~~~~ <<< Unknown tree: offset_type >>> <<< Unknown tree: offset_type >>> <<< Unknown tree: offset_type >>> _11 = _10 & Reset___trans_tmp_1.1_3; during GIMPLE pass: reassoc bug849.cc:14:6: internal compiler error: verify_gimple failed The bug first seems to occur sometime between git hash 7d7e2149cdb6b0c3 and 9a1bc4b463e61cd5, a day later. There are 24 commits in that range.
next reply other threads:[~2022-09-24 19:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-24 19:34 dcb314 at hotmail dot com [this message] 2022-09-24 20:07 ` [Bug c++/107029] [13 Regression] " jakub at gcc dot gnu.org 2022-09-25 12:52 ` [Bug tree-optimization/107029] " jakub at gcc dot gnu.org 2022-09-27 6:27 ` cvs-commit at gcc dot gnu.org 2022-09-27 11:08 ` jakub 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-107029-4@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).