public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111472] [11/12/13 Regression] Wrong code at -Os on x86_64-linux-gnu since r11-4563-gd0d8b5d836 Date: Thu, 07 Mar 2024 22:24:15 +0000 [thread overview] Message-ID: <bug-111472-4-88KTz3EKo2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111472-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111472 Jeffrey A. Law <law at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |law at gcc dot gnu.org Summary|[11/12/13/14 Regression] |[11/12/13 Regression] Wrong |Wrong code at -Os on |code at -Os on |x86_64-linux-gnu since |x86_64-linux-gnu since |r11-4563-gd0d8b5d836 |r11-4563-gd0d8b5d836 --- Comment #6 from Jeffrey A. Law <law at gcc dot gnu.org> --- Close. It was the next revision my bisection landed on as the fix: commit 9692309ed6b625f0fb358c0e230404b5603f69a6 (refs/bisect/bad) Author: Richard Biener <rguenther@suse.de> Date: Fri Oct 20 15:08:49 2023 +0200 tree-optimization/111445 - simple_iv simplification fault The following fixes a missed check in the simple_iv attempt to simplify (signed T)((unsigned T) base + step) where it allows a truncating inner conversion leading to wrong code. PR tree-optimization/111445 * tree-scalar-evolution.cc (simple_iv_with_niters): Add missing check for a sign-conversion. * gcc.dg/torture/pr111445.c: New testcase.
next prev parent reply other threads:[~2024-03-07 22:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-19 7:38 [Bug c/111472] New: Wrong code at -Os on x86_64-linux-gnu since shaohua.li at inf dot ethz.ch 2023-09-19 7:45 ` [Bug tree-optimization/111472] Wrong code at -Os on x86_64-linux-gnu since r11-4563-gd0d8b5d836 xry111 at gcc dot gnu.org 2023-09-19 7:47 ` shaohua.li at inf dot ethz.ch 2023-09-19 7:48 ` [Bug tree-optimization/111472] [11/12/13/14 Regression] " xry111 at gcc dot gnu.org 2023-09-19 7:48 ` pinskia at gcc dot gnu.org 2023-11-06 20:31 ` amacleod at redhat dot com 2023-11-06 20:35 ` amacleod at redhat dot com 2023-11-06 20:37 ` pinskia at gcc dot gnu.org 2024-03-07 22:24 ` law at gcc dot gnu.org [this message] 2024-05-08 12:15 ` [Bug tree-optimization/111472] [11 " 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-111472-4-88KTz3EKo2@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).