public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/94728] [haifa-sched][restore_pattern] recalculate INSN_TICK for the dependence type of REG_DEP_CONTROL Date: Thu, 23 Apr 2020 10:55:27 +0000 [thread overview] Message-ID: <bug-94728-4-0qd6Aa5rJz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94728-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94728 Alexander Monakov <amonakov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abel at gcc dot gnu.org Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Alexander Monakov <amonakov at gcc dot gnu.org> --- On the high level the analysis makes sense to me, but as this is predication in Haifa scheduler this is not really my domain :) The bugreport is also missing a testcase and information about the target. I see the reporter has just sent an email to the gcc@ mailing list, so I'm closing the report: https://gcc.gnu.org/pipermail/gcc/2020-April/232192.html
next prev parent reply other threads:[~2020-04-23 10:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-23 8:21 [Bug rtl-optimization/94728] New: " xuemaosheng at huawei dot com 2020-04-23 9:23 ` [Bug rtl-optimization/94728] " rguenth at gcc dot gnu.org 2020-04-23 9:26 ` xuemaosheng at huawei dot com 2020-04-23 10:55 ` amonakov at gcc dot gnu.org [this message] 2020-04-23 11:03 ` xuemaosheng at huawei dot com
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-94728-4-0qd6Aa5rJz@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).