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/111727] [14 Regression] wrong code at -O3 on x86_64-linux-gnu since r14-2944-g3d48c11ad082de
Date: Tue, 14 Nov 2023 14:13:56 +0000	[thread overview]
Message-ID: <bug-111727-4-lQ14xEuziZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111727-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111727

--- Comment #5 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:2066c29bf8dea87c9810eb261e342d941a6b2059

commit r14-5446-g2066c29bf8dea87c9810eb261e342d941a6b2059
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Nov 14 14:26:17 2023 +0100

    tree-optimization/111233 - loop splitting miscompile

    The change in r14-2852-gf5fb9ff2396fd4 failed to update patch_loop_exit
    to compensate for rewriting of a NE/EQ_EXPR to a new code.  Fixed
    with the following.

            PR tree-optimization/111233
            PR tree-optimization/111652
            PR tree-optimization/111727
            PR tree-optimization/111838
            PR tree-optimization/112113
            * tree-ssa-loop-split.cc (patch_loop_exit): Get the new
            guard code instead of the old guard stmt.
            (split_loop): Adjust.

            * gcc.dg/torture/pr111233.c: New testcase.
            * gcc.dg/torture/pr111652.c: Likewise.
            * gcc.dg/torture/pr111727.c: Likewise.
            * gcc.dg/torture/pr111838.c: Likewise.
            * gcc.dg/torture/pr112113.c: Likewise.

  parent reply	other threads:[~2023-11-14 14:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-08 16:34 [Bug tree-optimization/111727] New: wrong code at -O3 on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2023-10-08 16:50 ` [Bug tree-optimization/111727] [14 Regression] " pinskia at gcc dot gnu.org
2023-10-13  6:31 ` zhendong.su at inf dot ethz.ch
2023-10-17 13:06 ` rguenth at gcc dot gnu.org
2023-10-17 13:54 ` ppalka at gcc dot gnu.org
2023-11-14 14:13 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-14 14:15 ` [Bug tree-optimization/111727] [14 Regression] wrong code at -O3 on x86_64-linux-gnu since r14-2944-g3d48c11ad082de 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-111727-4-lQ14xEuziZ@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: link
Be 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).