public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/104510] [9/10/11/12 Regression] ICE: 'verify_gimple' failed: mismatching comparison operand types in verify_gimple_in_seq() Date: Mon, 14 Feb 2022 18:14:20 +0000 [thread overview] Message-ID: <bug-104510-4-RPI63MyvcC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104510-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104510 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 52439 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52439&action=edit gcc12-pr104510.patch Untested fix. Callers don't expect shorten_compare to ever fail, even when it returns NULL it still should convert arguments at least to the original *restype_ptr.
next prev parent reply other threads:[~2022-02-14 18:14 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-12 6:40 [Bug tree-optimization/104510] New: " zsojka at seznam dot cz 2022-02-13 4:48 ` [Bug c/104510] " pinskia at gcc dot gnu.org 2022-02-13 4:54 ` [Bug c/104510] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-02-14 8:34 ` rguenth at gcc dot gnu.org 2022-02-14 16:33 ` jakub at gcc dot gnu.org 2022-02-14 18:14 ` jakub at gcc dot gnu.org [this message] 2022-02-16 8:26 ` cvs-commit at gcc dot gnu.org 2022-02-16 9:23 ` [Bug c/104510] [9/10/11 " jakub at gcc dot gnu.org 2022-02-19 8:03 ` cvs-commit at gcc dot gnu.org 2022-02-19 8:09 ` [Bug c/104510] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:24 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:25 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` 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-104510-4-RPI63MyvcC@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).