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/112310] [14 Regression] Wrong code at -O2/3 on x86_64-linux-gnu since r14-1161-g5476de2618f
Date: Fri, 03 Nov 2023 10:35:37 +0000	[thread overview]
Message-ID: <bug-112310-4-NnoSBBlUwZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112310-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:2266f7cbc78dfcf7c0739466644e0a6b9966553c

commit r14-5095-g2266f7cbc78dfcf7c0739466644e0a6b9966553c
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Nov 3 10:45:18 2023 +0100

    tree-optimization/112310 - code hoisting undefined behavior

    The following avoids hoisting expressions that may invoke undefined
    behavior and are not computed on all paths.  This is realized by
    noting that we have to avoid materializing expressions as part
    of hoisting that are not part of the set of expressions we have
    found eligible for hoisting.  Instead of picking the expression
    corresponding to the hoistable values from the first successor
    we now keep a union of the expressions so that hoisting can pick
    the expression that has its dependences fully hoistable.

            PR tree-optimization/112310
            * tree-ssa-pre.cc (do_hoist_insertion): Keep the union
            of expressions, validate dependences are contained within
            the hoistable set before hoisting.

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

  parent reply	other threads:[~2023-11-03 10:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 11:13 [Bug tree-optimization/112310] New: " shaohua.li at inf dot ethz.ch
2023-10-31 12:02 ` [Bug tree-optimization/112310] " rguenth at gcc dot gnu.org
2023-10-31 12:03 ` rguenth at gcc dot gnu.org
2023-10-31 15:52 ` rguenth at gcc dot gnu.org
2023-11-03  9:40 ` rguenth at gcc dot gnu.org
2023-11-03 10:35 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-03 10:35 ` 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-112310-4-NnoSBBlUwZ@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).