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 target/111600] [14/15 Regression] RISC-V bootstrap time regression
Date: Tue, 30 Apr 2024 08:26:43 +0000	[thread overview]
Message-ID: <bug-111600-4-65tCDME7z4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111600-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #33 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:440a612dbadfae5887ec7c9b3ab2fca88b065366

commit r13-8662-g440a612dbadfae5887ec7c9b3ab2fca88b065366
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Sep 28 11:51:30 2023 +0200

    target/111600 - avoid deep recursion in access diagnostics

    pass_waccess::check_dangling_stores uses recursion to traverse the CFG.
    The following changes this to use a heap allocated worklist to avoid
    blowing the stack.

    Instead of using a better iteration order it tries hard to preserve
    the current iteration order to avoid new false positives to pop up
    since the set of stores we keep track isn't properly modeling flow,
    so what is diagnosed and what not is quite random.  We are also
    lacking the ideal RPO compute on the inverted graph that would just
    ignore reverse unreachable code (as the current iteration scheme does).

            PR target/111600
            * gimple-ssa-warn-access.cc (pass_waccess::check_dangling_stores):
            Use a heap allocated worklist for CFG traversal instead of
            recursion.

    (cherry picked from commit f194c684a28a5d449bd034a2c604d04ba465e4fe)

  parent reply	other threads:[~2024-04-30  8:26 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 13:35 [Bug target/111600] New: [14.0 regression] " schwab@linux-m68k.org
2023-09-26 17:41 ` [Bug target/111600] " pinskia at gcc dot gnu.org
2023-09-27  7:36 ` [Bug target/111600] [14 Regression] " rguenth at gcc dot gnu.org
2023-09-27  7:47 ` schwab@linux-m68k.org
2023-09-27  7:50 ` schwab@linux-m68k.org
2023-09-27  8:00 ` rguenth at gcc dot gnu.org
2023-09-27 13:36 ` schwab@linux-m68k.org
2023-09-27 17:50 ` palmer at gcc dot gnu.org
2023-09-27 18:22 ` schwab@linux-m68k.org
2023-09-28  8:06 ` schwab@linux-m68k.org
2023-09-28  9:47 ` rguenth at gcc dot gnu.org
2023-09-28 13:14 ` cvs-commit at gcc dot gnu.org
2023-10-02 15:03 ` rdapp at gcc dot gnu.org
2023-10-02 15:28 ` kito at gcc dot gnu.org
2023-10-03 15:26 ` kito at gcc dot gnu.org
2023-10-04  6:46 ` rguenth at gcc dot gnu.org
2023-10-04  8:17 ` rdapp at gcc dot gnu.org
2023-10-04  9:07 ` rguenther at suse dot de
2023-10-04 12:50 ` rdapp at gcc dot gnu.org
2023-10-04 13:13 ` rguenth at gcc dot gnu.org
2023-10-04 13:21 ` rdapp at gcc dot gnu.org
2023-10-04 13:56 ` rguenth at gcc dot gnu.org
2023-10-04 14:38 ` rdapp at gcc dot gnu.org
2023-10-12 11:50 ` rdapp at gcc dot gnu.org
2023-10-13  1:39 ` juzhe.zhong at rivai dot ai
2023-10-13  7:28 ` rdapp at gcc dot gnu.org
2023-10-13  8:01 ` rdapp at gcc dot gnu.org
2023-10-13  8:04 ` rguenther at suse dot de
2023-10-31 12:35 ` cvs-commit at gcc dot gnu.org
2023-11-01  2:24 ` juzhe.zhong at rivai dot ai
2023-11-02  9:31 ` rdapp at gcc dot gnu.org
2023-11-06 18:15 ` schwab@linux-m68k.org
2023-11-06 22:07 ` juzhe.zhong at rivai dot ai
2024-03-04  4:31 ` law at gcc dot gnu.org
2024-04-30  8:26 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-07  7:42 ` [Bug target/111600] [14/15 " 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-111600-4-65tCDME7z4@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).