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/101025] [11/12 Regression] wrong code at -O3 on x86_64-linux-gnu Date: Fri, 11 Jun 2021 09:08:44 +0000 [thread overview] Message-ID: <bug-101025-4-IniYEAuC7w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101025-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101025 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- The issue is with sm_seq_valid_bb which when processing store sequences from multiple branches of the CFG performs merging in a way that drops refs that still need to be considered for dependence queries. Notably /* Incrementally merge seqs into first_edge_seq. */ for (unsigned int i = 0; i < min_len; ++i) { /* ??? We can more intelligently merge when we face different order by additional sinking operations in one sequence. For now we simply mark them as to be processed by the not order-preserving SM code. */ if (first_edge_seq[i].first != edge_seq[i].first) { if (first_edge_seq[i].second == sm_ord) bitmap_set_bit (refs_not_supported, first_edge_seq[i].first); if (edge_seq[i].second == sm_ord) bitmap_set_bit (refs_not_supported, edge_seq[i].first); first_edge_seq[i].second = sm_other; first_edge_seq[i].from = NULL_TREE; we re matching f ={v} 0 against a[3] = ...;, marking 'f' as not supported for store-motion and to be dependence checked against all stores in the sequence. But we simply forget about a[3] = ... which we'd need to insert somehow into the sequence for dependence checking purposes similar to how we handle /* Any excess elements become sm_other since they are now coonditionally executed. */ if (first_edge_seq.length () > edge_seq.length ()) { (but even that code looks suspicious). What we'd need to verify is that we can push the ref down in 'edge_seq' (but not actually do that) and then append it like the late loop (but we need to disambiguate against the stores in first_edge_seq as well). The code is quite complex and as it handles dependence queries incrementally it's also fragile...
next prev parent reply other threads:[~2021-06-11 9:08 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-11 4:51 [Bug tree-optimization/101025] New: " qrzhang at gatech dot edu 2021-06-11 8:15 ` [Bug tree-optimization/101025] [11/12 Regression] " rguenth at gcc dot gnu.org 2021-06-11 8:27 ` rguenth at gcc dot gnu.org 2021-06-11 8:59 ` marxin at gcc dot gnu.org 2021-06-11 9:08 ` marxin at gcc dot gnu.org 2021-06-11 9:08 ` rguenth at gcc dot gnu.org [this message] 2021-06-11 16:13 ` cvs-commit at gcc dot gnu.org 2021-06-11 16:13 ` [Bug tree-optimization/101025] [11 " rguenth at gcc dot gnu.org 2021-06-11 16:26 ` qrzhang at gatech dot edu 2021-06-16 10:16 ` rguenth at gcc dot gnu.org 2021-07-07 14:06 ` cvs-commit at gcc dot gnu.org 2021-07-07 14:08 ` 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-101025-4-IniYEAuC7w@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).