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 c/104510] [9/10 Regression] ICE: 'verify_gimple' failed: mismatching comparison operand types in verify_gimple_in_seq() Date: Tue, 10 May 2022 08:24:13 +0000 [thread overview] Message-ID: <bug-104510-4-jCjiHUzBPO@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 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:83aea9cb28f729698a79e4262ef3a43a0fd79d4f commit r10-10683-g83aea9cb28f729698a79e4262ef3a43a0fd79d4f Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Feb 16 09:25:55 2022 +0100 c-family: Fix up shorten_compare for decimal vs. non-decimal float comparison [PR104510] The comment in shorten_compare says: /* If either arg is decimal float and the other is float, fail. */ but the callers of shorten_compare don't expect anything like failure as a possibility from the function, callers require that the function promotes the operands to the same type, whether the original selected *restype_ptr one or some shortened. So, if we choose not to shorten, we should still promote to the original *restype_ptr. 2022-02-16 Jakub Jelinek <jakub@redhat.com> PR c/104510 * c-common.c (shorten_compare): Convert original arguments to the original *restype_ptr when mixing binary and decimal float. * gcc.dg/dfp/pr104510.c: New test. (cherry picked from commit 6e74122f0de6748b3fd0ed9183090cd7c61fb53e)
next prev parent reply other threads:[~2022-05-10 8:24 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 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 [this message] 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-jCjiHUzBPO@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).