public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114209] ICE: verify_gimple failed: incorrect sharing of tree nodes at -O and above Date: Mon, 04 Mar 2024 10:15:59 +0000 [thread overview] Message-ID: <bug-114209-4-tkLpRyr5Ur@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114209-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114209 --- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:c27148f2f40654a638bcf429633be1c0561529d5 commit r14-9291-gc27148f2f40654a638bcf429633be1c0561529d5 Author: Jakub Jelinek <jakub@redhat.com> Date: Mon Mar 4 11:15:07 2024 +0100 bitint: Fix tree node sharing bug [PR114209] We ICE on the following testcase due to invalid tree sharing. The second hunk fixes that, the first one is from me looking around at other spots which might need end up with invalid tree sharing too. 2024-03-04 Jakub Jelinek <jakub@redhat.com> PR middle-end/114209 * gimple-lower-bitint.cc (bitint_large_huge::limb_access): Call unshare_expr when creating a MEM_REF from MEM_REF. (bitint_large_huge::lower_stmt): Call unshare_expr. * gcc.dg/bitint-97.c: New test.
next prev parent reply other threads:[~2024-03-04 10:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-02 13:10 [Bug middle-end/114209] New: " zsojka at seznam dot cz 2024-03-02 22:15 ` [Bug middle-end/114209] " pinskia at gcc dot gnu.org 2024-03-04 10:15 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-04 12:34 ` 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-114209-4-tkLpRyr5Ur@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).