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 middle-end/54052] [11/12/13 Regression] g++ takes excessive time in opt and generate phase; can lead to Segmentation Fault when not enough memory available Date: Mon, 13 May 2024 12:44:00 +0000 [thread overview] Message-ID: <bug-54052-4-wXgRVdwyii@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54052-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54052 --- Comment #16 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:d629308c699bb8fe90c2afeb7fa1acb12cb5526b commit r13-8763-gd629308c699bb8fe90c2afeb7fa1acb12cb5526b Author: Richard Biener <rguenther@suse.de> Date: Mon Feb 19 11:10:50 2024 +0100 rtl-optimization/54052 - RTL SSA PHI insertion compile-time hog The following tries to address the PHI insertion compile-time hog in RTL fwprop observed with the PR54052 testcase where the loop computing the "unfiltered" set of variables possibly needing PHI nodes for each block exhibits quadratic compile-time and memory-use. It does so by pruning the local DEFs with LR_OUT of the block, removing regs that can never be LR_IN (defined by this block) in the dominance frontier. PR rtl-optimization/54052 * rtl-ssa/blocks.cc (function_info::place_phis): Filter local defs by LR_OUT. (cherry picked from commit c7151283dc747769d4ac4f216d8f519bda2569b5)
next prev parent reply other threads:[~2024-05-13 12:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-20 14:39 [Bug c++/54052] New: Segmentation Fault baxter at about dot org 2012-07-24 16:04 ` [Bug c++/54052] " baxter at about dot org 2012-07-24 16:19 ` redi at gcc dot gnu.org 2012-07-24 18:29 ` baxter at about dot org 2012-07-24 18:37 ` redi at gcc dot gnu.org 2012-07-24 20:34 ` baxter at about dot org 2013-05-05 11:57 ` paolo.carlini at oracle dot com 2024-02-16 14:49 ` [Bug c++/54052] [11/12/13/14 Regression] g++ takes excessive time in opt and generate phase; can lead to Segmentation Fault when not enough memory available rguenth at gcc dot gnu.org 2024-02-19 9:27 ` [Bug middle-end/54052] " rguenth at gcc dot gnu.org 2024-02-19 10:14 ` rguenth at gcc dot gnu.org 2024-02-19 10:40 ` rguenth at gcc dot gnu.org 2024-02-19 13:42 ` cvs-commit at gcc dot gnu.org 2024-02-19 13:44 ` [Bug middle-end/54052] [11/12/13 " rguenth at gcc dot gnu.org 2024-05-13 11:39 ` rguenth at gcc dot gnu.org 2024-05-13 12:44 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-12 12:33 ` [Bug middle-end/54052] [11/12 " cvs-commit 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-54052-4-wXgRVdwyii@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).