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
Date: Tue, 22 Jun 2021 08:47:01 +0000 [thread overview]
Message-ID: <bug-101162-4-LRSAOzD4JI@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
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c++ |tree-optimization
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>This regression was introduced between 2021-06-14 and 2021-06-21.
I added the extra checks during that time period.
But the problem was latent before hand. Multiplying on offset_type does not
make sense.
next prev parent reply other threads:[~2021-06-22 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 8:40 [Bug c++/101162] New: " 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 ` pinskia at gcc dot gnu.org [this message]
2021-06-22 9:07 ` [Bug tree-optimization/101162] " jakub at gcc dot gnu.org
2021-06-22 9:11 ` [Bug tree-optimization/101162] [12 Regression] ICE (verify_gimple failed) for switch returning pointer-to-members since r12-1608 pinskia at gcc dot gnu.org
2021-06-22 9:12 ` 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-LRSAOzD4JI@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: link
Be 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).