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 middle-end/103248] [12 Regression] ICE in operation_could_trap_helper_p, at tree-eh.c:2479 Date: Thu, 17 Feb 2022 11:57:04 +0000 [thread overview] Message-ID: <bug-103248-4-LqMsS6Qst5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103248-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103248 --- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:1ac5fbea476e4ebd6a0086ccfbf92e648768be7b commit r9-9955-g1ac5fbea476e4ebd6a0086ccfbf92e648768be7b Author: Richard Biener <rguenther@suse.de> Date: Thu Nov 11 09:40:36 2021 +0100 middle-end/103181 - fix operation_could_trap_p for vector division For integer vector division we only checked for all zero vector constants rather than checking whether any element in the constant vector is zero. It also fixes the adjustment to operation_could_trap_helper_p where I failed to realize that RDIV_EXPR is also used for fixed-point types. It also fixes that handling by properly checking for a fixed_zerop divisor. 2021-11-11 Richard Biener <rguenther@suse.de> PR middle-end/103181 PR middle-end/103248 * tree-eh.c (operation_could_trap_helper_p): Properly check vector constants for a zero element for integer division. Separate floating point and integer division code. Properly handle fixed-point RDIV_EXPR. * gcc.dg/torture/pr103181.c: New testcase. * gcc.dg/pr103248.c: Likewise. (cherry picked from commit 2f0c8f74daef93c0c7b33294213e7db6df58c4d1)
prev parent reply other threads:[~2022-02-17 11:57 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-15 11:11 [Bug target/103248] New: " marxin at gcc dot gnu.org 2021-11-15 11:21 ` [Bug target/103248] " pinskia at gcc dot gnu.org 2021-11-15 11:24 ` marxin at gcc dot gnu.org 2021-11-15 12:12 ` rguenth at gcc dot gnu.org 2021-11-15 12:16 ` marxin at gcc dot gnu.org 2021-11-15 12:26 ` rguenth at gcc dot gnu.org 2021-11-15 12:33 ` marxin at gcc dot gnu.org 2021-11-15 12:54 ` jakub at gcc dot gnu.org 2021-11-16 9:26 ` rguenth at gcc dot gnu.org 2021-11-16 9:30 ` marxin at gcc dot gnu.org 2021-11-16 9:30 ` marxin at gcc dot gnu.org 2021-11-16 10:44 ` [Bug middle-end/103248] " rguenth at gcc dot gnu.org 2021-11-16 12:49 ` [Bug middle-end/103248] [12 Regression] " rguenth at gcc dot gnu.org 2021-11-17 0:32 ` joseph at codesourcery dot com 2021-11-19 8:36 ` cvs-commit at gcc dot gnu.org 2021-11-19 8:36 ` rguenth at gcc dot gnu.org 2021-11-22 8:00 ` cvs-commit at gcc dot gnu.org 2022-02-17 10:48 ` cvs-commit at gcc dot gnu.org 2022-02-17 11:57 ` cvs-commit at gcc dot gnu.org [this message]
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-103248-4-LqMsS6Qst5@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).