public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115256] [15 Regression] 502.gcc_r Run failed with '-march=native -Ofast -funroll-loops -flto' since r15-571-g1e0ae1f52741f7 Date: Tue, 28 May 2024 12:02:40 +0000 [thread overview] Message-ID: <bug-115256-4-7mIbcyfLuT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115256-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115256 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed on Zen3 btw, fails with the test input already. Note that this may still be a latent issue in 502.gcc_r. -funroll-loops isn't neccessary, -O3 -flto was enough to reproduce (no specific sub-architecture required). -fno-strict-aliasing avoids the issue. --param dse-max-object-size=0 doesn't help (turn off live byte tracking) The patch itself likely adds quite some extra DSE so that's too much to track down. DSE doesn't have a debug counter at the moment, but "bisecting" --param dse-max-alias-queries-per-store shows the issue still happens with 64 but not with 48. The issue still reproduces with -flto-partition=1to1 (if one wants to try per-TU compile flags) and with -flto-partition=one (if you want to add a debug counter and bisect the bad store, but =one is slow). We ICE in cfgloopmanip.c:create_preheader here: basic_block create_preheader (struct loop *loop, int flags) { edge e, fallthru; basic_block dummy; int nentry = 0; bool irred = false; bool latch_edge_was_fallthru; edge one_succ_pred = NULL, single_entry = NULL; edge_iterator ei; FOR_EACH_EDGE (e, ei, loop->header->preds) { if (e->src == loop->latch) continue; irred |= (e->flags & EDGE_IRREDUCIBLE_LOOP) != 0; nentry++; single_entry = e; if (single_succ_p (e->src)) one_succ_pred = e; } gcc_assert (nentry); ^^^ placing noinline on the above function still reproduces the issue. We seem to run the above for the loop tree root but call from create_preheaders which does 1425 FOR_EACH_LOOP (li, loop, 0) 1426 create_preheader (loop, flags); (note absence of LI_INCLUDE_ROOT) so somehow the loop iterator setup is broken.
next prev parent reply other threads:[~2024-05-28 12:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-28 9:05 [Bug tree-optimization/115256] New: " admin at levyhsu dot com 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 [this message] 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-7mIbcyfLuT@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).