public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "admin at levyhsu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/115256] New: [15 Regression] 502.gcc_r Run failed with '-march=native -Ofast -funroll-loops -flto' since r15-571-g1e0ae1f52741f7
Date: Tue, 28 May 2024 09:05:25 +0000	[thread overview]
Message-ID: <bug-115256-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 115256
           Summary: [15 Regression] 502.gcc_r Run failed with
                    '-march=native -Ofast -funroll-loops -flto' since
                    r15-571-g1e0ae1f52741f7
           Product: gcc
           Version: 15.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: admin at levyhsu dot com
  Target Milestone: ---

Bisect down to r15-571-g1e0ae1f52741f7
(1e0ae1f52741f7e0133661659ed2d210f939a398)

tree-optimization/79958 - make DSE track multiple paths
DSE currently gives up when the path we analyze forks.  This leads
to multiple missed dead store elimination PRs.  The following fixes
this by recursing for each path and maintaining the visited bitmap
to avoid visiting CFG re-merges multiple times.  The overall cost
is still limited by the same bound, it's just more likely we'll hit
the limit now.  The patch doesn't try to deal with byte tracking
once a path forks but drops info on the floor and only handling
fully dead stores in that case.

        PR tree-optimization/79958
        PR tree-optimization/109087
        PR tree-optimization/100314
        PR tree-optimization/114774
        * tree-ssa-dse.cc (dse_classify_store): New forwarder.
        (dse_classify_store): Add arguments cnt and visited, recurse
        to track multiple paths when we end up with multiple defs.

        * gcc.dg/tree-ssa/ssa-dse-48.c: New testcase.
        * gcc.dg/tree-ssa/ssa-dse-49.c: Likewise.
        * gcc.dg/tree-ssa/ssa-dse-50.c: Likewise.
        * gcc.dg/tree-ssa/ssa-dse-51.c: Likewise.
        * gcc.dg/graphite/pr80906.c: Avoid DSE of last data reference
        in loop.
        * g++.dg/ipa/devirt-24.C: Adjust for extra DSE.
        * g++.dg/warn/Wuninitialized-pr107919-1.C: Use more important
        -O2 optimization level, -O1 regresses.

Observed on 
Ice Lake
Cascade Lake
AlderLake
Zen3 Server/Client
Also failed on Aarch64 (But didn't bisect)

             reply	other threads:[~2024-05-28  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28  9:05 admin at levyhsu dot com [this message]
2024-05-28 10:46 ` [Bug tree-optimization/115256] " rguenth at gcc dot gnu.org
2024-05-28 12:02 ` rguenth at gcc dot gnu.org
2024-05-28 13:28 ` admin at levyhsu dot com
2024-06-17  7:41 ` hongyuw at gcc dot gnu.org
2024-06-17 12:45 ` 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-115256-4@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).