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/105969] [12 Regression] ICE in Floating point exception since r13-750-g10d1986aee47c5 Date: Tue, 19 Jul 2022 11:38:09 +0000 [thread overview] Message-ID: <bug-105969-4-sxwAYuTdCO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105969-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105969 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:4f34a9e8d5ffcef99a212180d58718b00bdbb7d2 commit r12-8579-g4f34a9e8d5ffcef99a212180d58718b00bdbb7d2 Author: Richard Biener <rguenther@suse.de> Date: Wed Jun 15 10:54:48 2022 +0200 tree-optimization/105969 - FPE with array diagnostics For a [0][0] array we have to be careful when dividing by the element size which is zero for the outermost dimension. Luckily the division is only for an overflow check which is pointless for array size zero. 2022-06-15 Richard Biener <rguenther@suse.de> PR tree-optimization/105969 * gimple-ssa-sprintf.cc (get_origin_and_offset_r): Avoid division by zero in overflow check. * gcc.dg/pr105969.c: New testcase. (cherry picked from commit edb9330c29fe8a0a0b76df6fafd6a223a4d0e41f)
next prev parent reply other threads:[~2022-07-19 11:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-14 10:23 [Bug c/105969] New: [12/13 Regression] ICE in Floating point exception gscfq@t-online.de 2022-06-15 8:50 ` [Bug c/105969] " rguenth at gcc dot gnu.org 2022-06-15 11:15 ` cvs-commit at gcc dot gnu.org 2022-06-15 15:57 ` [Bug c/105969] [12 " joseph at codesourcery dot com 2022-07-15 8:58 ` [Bug c/105969] [12 Regression] ICE in Floating point exception since r13-750-g10d1986aee47c5 marxin at gcc dot gnu.org 2022-07-19 11:38 ` cvs-commit at gcc dot gnu.org [this message] 2022-07-19 11:39 ` 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-105969-4-sxwAYuTdCO@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).