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/109637] unnecessary range check in complete switch on bitfield Date: Fri, 11 Aug 2023 00:17:48 +0000 [thread overview] Message-ID: <bug-109637-4-Sx4e02FI42@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109637-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109637 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Mine. For the simple example in comment #0, I have a patch. This is the updating of test_for_singularity patch. For the GIMPLE_SWITCH issue in EVRP, I suspect the code in vr-values.c needs to update and/or added to see if the default was taken or not. I will handle this too.
next prev parent reply other threads:[~2023-08-11 0:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-26 18:17 [Bug middle-end/109637] New: " mattiase at acm dot org 2023-04-26 18:19 ` [Bug middle-end/109637] " pinskia at gcc dot gnu.org 2023-04-26 18:28 ` [Bug tree-optimization/109637] " pinskia at gcc dot gnu.org 2023-04-26 18:52 ` amacleod at redhat dot com 2023-04-26 19:02 ` amacleod at redhat dot com 2023-04-26 19:05 ` pinskia at gcc dot gnu.org 2023-04-26 19:16 ` amacleod at redhat dot com 2023-08-11 0:17 ` pinskia at gcc dot gnu.org [this message] 2023-08-11 0:39 ` pinskia 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-109637-4-Sx4e02FI42@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).