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/104931] [9/10/11 Regression] wrong-code with number_of_iterations_lt_to_ne Date: Wed, 23 Mar 2022 14:08:08 +0000 [thread overview] Message-ID: <bug-104931-4-RI8FlkM8Jo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104931-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104931 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:d1f4dfd409dedf4d00ca7be001cf757d0d6e82f4 commit r11-9688-gd1f4dfd409dedf4d00ca7be001cf757d0d6e82f4 Author: Richard Biener <rguenther@suse.de> Date: Wed Mar 16 14:53:06 2022 +0100 tree-optimization/104931 - mitigate niter analysis issue The following backports a pointer associating pattern from trunk that mitigates an issue with number_of_iterations_lt_to_ne in which context we fail to fold a comparison but succeed in folding a related subtraction. In the failure mode this results in a loop wrongly assumed looping with a bogus number of iterations, resulting in crashing of the premake application on start. With the backported simplification we are able to fold the comparison and correctly compute the loop as not iterating. I have failed to create a standalone testcase. I belive part of the issue is still latent but I have failed to nail down the issue exactly. Still I believe the backporting of the mitigation patch is the most sensible and safe thing at this point. 2022-03-16 Richard Biener <rguenther@suse.de> PR tree-optimization/104931 * match.pd ((ptr) (x p+ y) p+ z -> (ptr) (x p+ (y + z))): New GENERIC simplification.
next prev parent reply other threads:[~2022-03-23 14:08 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-15 10:20 [Bug tree-optimization/104931] New: " rguenth at gcc dot gnu.org 2022-03-15 10:20 ` [Bug tree-optimization/104931] " rguenth at gcc dot gnu.org 2022-03-15 10:37 ` rguenth at gcc dot gnu.org 2022-03-15 13:11 ` rguenth at gcc dot gnu.org 2022-03-16 12:34 ` rguenth at gcc dot gnu.org 2022-03-16 13:09 ` rguenth at gcc dot gnu.org 2022-03-16 13:14 ` [Bug tree-optimization/104931] [9/10/11 Regression] " rguenth at gcc dot gnu.org 2022-03-16 13:32 ` rguenth at gcc dot gnu.org 2022-03-17 13:45 ` rguenth at gcc dot gnu.org 2022-03-17 13:46 ` rguenth at gcc dot gnu.org 2022-03-17 13:53 ` rguenth at gcc dot gnu.org 2022-03-17 14:27 ` rguenth at gcc dot gnu.org 2022-03-23 14:08 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-27 9:47 ` [Bug tree-optimization/104931] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2023-07-07 9:58 ` 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-104931-4-RI8FlkM8Jo@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).