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/112344] [14 Regression] Wrong code at -O2 on x86_64-pc-linux-gnu Date: Wed, 22 Nov 2023 14:40:58 +0000 [thread overview] Message-ID: <bug-112344-4-zD1ZnvNS5E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112344-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112344 --- Comment #10 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:6bf66276e3e41d5d92f7b7260e98b6a111653805 commit r14-5759-g6bf66276e3e41d5d92f7b7260e98b6a111653805 Author: Richard Biener <rguenther@suse.de> Date: Wed Nov 22 11:10:41 2023 +0100 tree-optimization/112344 - wrong final value replacement When performing final value replacement chrec_apply that's used to compute the overall effect of niters to a CHREC doesn't consider that the overall increment of { -2147483648, +, 2 } doesn't fit in a signed integer when the loop iterates until the value of the IV of 20. The following fixes this mistake, carrying out the multiply and add in an unsigned type instead, avoiding undefined overflow and thus later miscompilation by path range analysis. PR tree-optimization/112344 * tree-chrec.cc (chrec_apply): Perform the overall increment calculation and increment in an unsigned type. * gcc.dg/torture/pr112344.c: New testcase.
next prev parent reply other threads:[~2023-11-22 14:40 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-02 6:30 [Bug middle-end/112344] New: " jwzeng at nuaa dot edu.cn 2023-11-02 6:41 ` [Bug middle-end/112344] " pinskia at gcc dot gnu.org 2023-11-02 6:42 ` pinskia at gcc dot gnu.org 2023-11-02 6:47 ` jwzeng at nuaa dot edu.cn 2023-11-02 6:49 ` pinskia at gcc dot gnu.org 2023-11-02 10:06 ` rguenth at gcc dot gnu.org 2023-11-21 19:22 ` jakub at gcc dot gnu.org 2023-11-21 19:23 ` jakub at gcc dot gnu.org 2023-11-22 7:43 ` rguenth at gcc dot gnu.org 2023-11-22 9:10 ` rguenth at gcc dot gnu.org 2023-11-22 10:06 ` rguenth at gcc dot gnu.org 2023-11-22 14:40 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-22 14:41 ` rguenth at gcc dot gnu.org 2023-11-24 7:50 ` cvs-commit at gcc dot gnu.org 2024-02-18 10:07 ` cvs-commit 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-112344-4-zD1ZnvNS5E@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).