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/107833] [12 Regression] wrong code at -Os and above on x86_64-linux-gnu since r12-5138-ge82c382971664d6f Date: Mon, 12 Dec 2022 11:20:59 +0000 [thread overview] Message-ID: <bug-107833-4-rNGq4eJs6s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107833-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107833 --- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:812847a9d12c0b65695cbe1a23959b69a7e62355 commit r12-8977-g812847a9d12c0b65695cbe1a23959b69a7e62355 Author: Richard Biener <rguenther@suse.de> Date: Fri Dec 2 14:52:20 2022 +0100 tree-optimization/107833 - invariant motion of uninit uses The following fixes a wrong-code bug caused by loop invariant motion hoisting an expression using an uninitialized value outside of its controlling condition causing IVOPTs to use that to rewrite a defined value. PR107839 is a similar case involving a bogus uninit diagnostic. PR tree-optimization/107833 PR tree-optimization/107839 * cfghooks.cc: Include tree.h. * tree-ssa-loop-im.cc (movement_possibility): Wrap and make stmts using any ssa_name_maybe_undef_p operand to preserve execution. (loop_invariant_motion_in_fun): Call mark_ssa_maybe_undefs to init maybe-undefined status. * tree-ssa-loop-ivopts.cc (ssa_name_maybe_undef_p, ssa_name_set_maybe_undef, ssa_name_any_use_dominates_bb_p, mark_ssa_maybe_undefs): Move ... * tree-ssa.cc: ... here. * tree-ssa.h (ssa_name_any_use_dominates_bb_p, mark_ssa_maybe_undefs): Declare. (ssa_name_maybe_undef_p, ssa_name_set_maybe_undef): Define. * gcc.dg/torture/pr107833.c: New testcase. * gcc.dg/uninit-pr107839.c: Likewise. (cherry picked from commit 44c8402d35160515b3c09fd2bc239587e0c32a2b)
next prev parent reply other threads:[~2022-12-12 11:21 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-23 12:48 [Bug tree-optimization/107833] New: wrong code at -Os and above on x86_64-linux-gnu zhendong.su at inf dot ethz.ch 2022-11-23 13:14 ` [Bug tree-optimization/107833] wrong code at -Os and above on x86_64-linux-gnu since r12-5138-ge82c382971664d6f marxin at gcc dot gnu.org 2022-11-23 14:12 ` aldyh at gcc dot gnu.org 2022-11-23 14:17 ` marxin at gcc dot gnu.org 2022-11-23 15:07 ` aldyh at gcc dot gnu.org 2022-11-23 19:22 ` marxin at gcc dot gnu.org 2022-11-23 20:56 ` [Bug tree-optimization/107833] [12/13 Regression] " rguenth at gcc dot gnu.org 2022-12-01 16:14 ` jakub at gcc dot gnu.org 2022-12-01 16:52 ` jakub at gcc dot gnu.org 2022-12-01 17:32 ` jakub at gcc dot gnu.org 2022-12-01 19:54 ` pinskia at gcc dot gnu.org 2022-12-02 8:19 ` rguenth at gcc dot gnu.org 2022-12-02 10:16 ` jakub at gcc dot gnu.org 2022-12-02 13:24 ` rguenther at suse dot de 2022-12-02 13:55 ` rguenth at gcc dot gnu.org 2022-12-05 9:32 ` cvs-commit at gcc dot gnu.org 2022-12-12 11:20 ` cvs-commit at gcc dot gnu.org [this message] 2022-12-12 11:22 ` [Bug tree-optimization/107833] [12 " 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-107833-4-rNGq4eJs6s@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).