public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110721] Segmentation fault with '-O3 -fno-dce -fno-ipa-cp -fno-tree-dce -fno-tree-sink'
Date: Mon, 23 Oct 2023 15:26:03 +0000	[thread overview]
Message-ID: <bug-110721-4-RvGiI092s9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110721-4@http.gcc.gnu.org/bugzilla/>

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

Sam James <sjames at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org
           Keywords|needs-bisection             |

--- Comment #5 from Sam James <sjames at gcc dot gnu.org> ---
the bisect indicates r12-248-gb58dc0b803057c was the fix:

b58dc0b803057c0e6032e0d9bd92cd834f72c75c is the first bad commit
commit b58dc0b803057c0e6032e0d9bd92cd834f72c75c
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Apr 27 14:32:27 2021 +0200

    tree-optimization/99912 - delete trivially dead stmts during DSE

    DSE performs a backwards walk over stmts removing stores but it
    leaves removing resulting dead SSA defs to later passes.  This
    eats into its own alias walking budget if the removed stores kept
    loads live.  The following patch adds removal of trivially dead
    SSA defs which helps in this situation and reduces the amount of
    garbage followup passes need to deal with.

  parent reply	other threads:[~2023-10-23 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 15:09 [Bug c/110721] New: " 19373742 at buaa dot edu.cn
2023-07-18 15:10 ` [Bug c/110721] " 19373742 at buaa dot edu.cn
2023-07-18 16:04 ` pinskia at gcc dot gnu.org
2023-07-19  6:39 ` [Bug middle-end/110721] " rguenth at gcc dot gnu.org
2023-10-23  9:25 ` sjames at gcc dot gnu.org
2023-10-23 15:26 ` sjames at gcc dot gnu.org [this message]
2023-10-23 17:30 ` pinskia at gcc dot gnu.org
2023-10-23 18:18 ` sjames 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-110721-4-RvGiI092s9@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).