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/112320] [14 Regression] crash from insert_debug_temp_for_var_def since r14-5032-ge3da1d7bb288c8 Date: Thu, 02 Nov 2023 10:31:13 +0000 [thread overview] Message-ID: <bug-112320-4-zVrOvJbv02@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112320-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112320 --- Comment #13 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:c05f748218a0d556972212d6aecfce0eb4c8a31c commit r14-5075-gc05f748218a0d556972212d6aecfce0eb4c8a31c Author: Richard Biener <rguenther@suse.de> Date: Thu Nov 2 10:39:03 2023 +0100 tree-optimization/112320 - bougs debug IL after SCCP The following addresses wrong debug IL created by SCCP rewriting stmts to defined overflow. I addressed another inefficiency there but needed to adjust the API of rewrite_to_defined_overflow for this which is now taking a stmt iterator for in-place operation and a stmt for sequence producing because gsi_for_stmt doesn't work for stmts not in the IL. PR tree-optimization/112320 * gimple-fold.h (rewrite_to_defined_overflow): New overload for in-place operation. * gimple-fold.cc (rewrite_to_defined_overflow): Add stmt iterator argument to worker, define separate API for in-place and not in-place operation. * tree-if-conv.cc (predicate_statements): Simplify. * tree-scalar-evolution.cc (final_value_replacement_loop): Likewise. * tree-ssa-ifcombine.cc (pass_tree_ifcombine::execute): Adjust. * tree-ssa-reassoc.cc (update_range_test): Likewise. * gcc.dg/pr112320.c: New testcase.
next prev parent reply other threads:[~2023-11-02 10:31 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-31 17:31 [Bug c/112320] New: crash from insert_debug_temp_for_var_def dcb314 at hotmail dot com 2023-10-31 17:35 ` [Bug tree-optimization/112320] [14 Regression] " pinskia at gcc dot gnu.org 2023-10-31 18:37 ` dcb314 at hotmail dot com 2023-10-31 18:47 ` dcb314 at hotmail dot com 2023-10-31 19:46 ` [Bug tree-optimization/112320] [14 Regression] crash from insert_debug_temp_for_var_def since r14-5032-ge3da1d7bb288c8 pinskia at gcc dot gnu.org 2023-10-31 22:21 ` hp at gcc dot gnu.org 2023-11-01 0:39 ` law at gcc dot gnu.org 2023-11-01 0:40 ` law at gcc dot gnu.org 2023-11-01 7:32 ` dcb314 at hotmail dot com 2023-11-01 11:28 ` pinskia at gcc dot gnu.org 2023-11-01 22:45 ` pinskia at gcc dot gnu.org 2023-11-02 8:29 ` rguenth at gcc dot gnu.org 2023-11-02 8:41 ` pinskia at gcc dot gnu.org 2023-11-02 8:42 ` pinskia at gcc dot gnu.org 2023-11-02 10:31 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-02 10:31 ` 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-112320-4-zVrOvJbv02@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).