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/114551] [14 Regression] wrong code at -O3 on x86_64-linux-gnu since r14-2944
Date: Thu, 04 Apr 2024 07:00:20 +0000	[thread overview]
Message-ID: <bug-114551-4-dvBaxwpMJW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114551-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from GCC 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:e152177b362143465e2b9d721ea632cae3f13445

commit r14-9781-ge152177b362143465e2b9d721ea632cae3f13445
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Apr 3 14:53:30 2024 +0200

    tree-optimization/114551 - loop splitting and undefined overflow

    When loop splitting hoists a guard computation it needs to make sure
    that can be safely evaluated at this place when it was previously
    only conditionally evaluated.  The following fixes this for the
    case of undefined overflow.

            PR tree-optimization/114551
            * tree-ssa-loop-split.cc (split_loop): If the guard is
            only conditionally evaluated rewrite computations with
            possibly undefined overflow to unsigned arithmetic.

            * gcc.dg/torture/pr114551.c: New testcase.

  parent reply	other threads:[~2024-04-04  7:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 19:31 [Bug tree-optimization/114551] New: wrong code at -O3 on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2024-04-01 20:45 ` [Bug tree-optimization/114551] [14 Regression] " pinskia at gcc dot gnu.org
2024-04-02 11:33 ` rguenth at gcc dot gnu.org
2024-04-02 13:22 ` jakub at gcc dot gnu.org
2024-04-02 23:43 ` [Bug tree-optimization/114551] [14 Regression] wrong code at -O3 on x86_64-linux-gnu since r14-2944 pinskia at gcc dot gnu.org
2024-04-03  3:44 ` pinskia at gcc dot gnu.org
2024-04-03  3:46 ` pinskia at gcc dot gnu.org
2024-04-03 12:27 ` rguenth at gcc dot gnu.org
2024-04-04  7:00 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-04  7:01 ` [Bug tree-optimization/114551] [13 " rguenth at gcc dot gnu.org
2024-05-06 12:06 ` [Bug tree-optimization/114551] [14 " 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-114551-4-dvBaxwpMJW@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).