public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101162] [12 Regression] ICE (verify_gimple failed) for switch returning pointer-to-members since r12-1608 Date: Tue, 22 Jun 2021 09:11:17 +0000 [thread overview] Message-ID: <bug-101162-4-B6mpRzgSvw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101162-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101162 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I was just about to assign this to myself as I had just came up with a fix: diff --git a/gcc/fold-const.c b/gcc/fold-const.c index 85e90f42b8e..5e4bdeace1e 100644 --- a/gcc/fold-const.c +++ b/gcc/fold-const.c @@ -5361,7 +5361,7 @@ range_check_type (tree etype) else return NULL_TREE; } - else if (POINTER_TYPE_P (etype)) + else if (POINTER_TYPE_P (etype) || TREE_CODE (etype) == OFFSET_TYPE) etype = unsigned_type_for (etype); return etype; }
next prev parent reply other threads:[~2021-06-22 9:11 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-22 8:40 [Bug c++/101162] New: [12 Regression] ICE (verify_gimple failed) for switch returning pointer-to-members reichelt at gcc dot gnu.org 2021-06-22 8:45 ` [Bug c++/101162] " pinskia at gcc dot gnu.org 2021-06-22 8:47 ` [Bug tree-optimization/101162] " pinskia at gcc dot gnu.org 2021-06-22 9:07 ` jakub at gcc dot gnu.org 2021-06-22 9:11 ` pinskia at gcc dot gnu.org [this message] 2021-06-22 9:12 ` [Bug tree-optimization/101162] [12 Regression] ICE (verify_gimple failed) for switch returning pointer-to-members since r12-1608 jakub at gcc dot gnu.org 2021-06-22 12:30 ` marxin at gcc dot gnu.org 2021-06-22 13:23 ` cvs-commit at gcc dot gnu.org 2021-07-18 10:41 ` 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-101162-4-B6mpRzgSvw@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).