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 tree-optimization/103181] [9/10/11/12 Regression] wrong code at -O1 due to conditional division by 0 being executed Date: Thu, 11 Nov 2021 09:33:02 +0000 [thread overview] Message-ID: <bug-103181-4-01n2OUxTbX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103181-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103181 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:a5fed4063f428a14f5b91533d5954b9bf4e3e7db commit r12-5149-ga5fed4063f428a14f5b91533d5954b9bf4e3e7db 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. 2021-11-11 Richard Biener <rguenther@suse.de> PR middle-end/103181 * 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. * gcc.dg/torture/pr103181.c: New testcase.
next prev parent reply other threads:[~2021-11-11 9:33 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-11 4:47 [Bug tree-optimization/103181] New: " zsojka at seznam dot cz 2021-11-11 5:01 ` [Bug tree-optimization/103181] " pinskia at gcc dot gnu.org 2021-11-11 5:12 ` pinskia at gcc dot gnu.org 2021-11-11 5:18 ` pinskia at gcc dot gnu.org 2021-11-11 8:03 ` rguenth at gcc dot gnu.org 2021-11-11 8:33 ` rguenth at gcc dot gnu.org 2021-11-11 9:18 ` rguenth at gcc dot gnu.org 2021-11-11 9:33 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-19 8:36 ` [Bug tree-optimization/103181] [9/10/11 " rguenth at gcc dot gnu.org 2021-11-22 8:00 ` cvs-commit at gcc dot gnu.org 2022-02-17 10:48 ` [Bug tree-optimization/103181] [9/10 " cvs-commit at gcc dot gnu.org 2022-02-17 11:57 ` [Bug tree-optimization/103181] [9 " cvs-commit at gcc dot gnu.org 2022-02-17 11:57 ` rguenth 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-103181-4-01n2OUxTbX@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).