public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "251078896 at qq dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/99101] optimization bug with -ffinite-loops Date: Mon, 15 Feb 2021 10:25:40 +0000 [thread overview] Message-ID: <bug-99101-4-oyDIywzPqr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99101-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99101 --- Comment #3 from Rex <251078896 at qq dot com> --- Dear Richard, Your post is informative, but I can't follow them all. Where does those "<bb 2>", "basic block 14", "local count" come from? I'm very interested in this kind of analysis (and tools). Could you give a hint to me? Thank you very much.(In reply to Richard Biener from comment #2) > And the heuristic in post-dom compute for infinite loops does not trigger > because we do have an exit from the loop via EH which is noreturn and the > processing > of those CFG dead-ends first makes the loop reverse reachable but makes > post-dominance "wrong". > > Bin, you poked into this code recently as well, just in case you have any > thoughts. > > It might be that control dependence calculation should not use post > dominators. (In reply to Richard Biener from comment #2) > And the heuristic in post-dom compute for infinite loops does not trigger > because we do have an exit from the loop via EH which is noreturn and the > processing > of those CFG dead-ends first makes the loop reverse reachable but makes > post-dominance "wrong". > > Bin, you poked into this code recently as well, just in case you have any > thoughts. > > It might be that control dependence calculation should not use post > dominators.
next prev parent reply other threads:[~2021-02-15 10:25 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-15 8:55 [Bug c++/99101] New: " 251078896 at qq dot com 2021-02-15 9:43 ` [Bug tree-optimization/99101] " rguenth at gcc dot gnu.org 2021-02-15 10:17 ` rguenth at gcc dot gnu.org 2021-02-15 10:25 ` 251078896 at qq dot com [this message] 2021-02-15 10:29 ` jakub at gcc dot gnu.org 2021-02-15 10:38 ` rguenth at gcc dot gnu.org 2021-02-15 10:46 ` rguenth at gcc dot gnu.org 2021-02-15 13:08 ` rguenth at gcc dot gnu.org 2021-02-24 14:00 ` rguenth at gcc dot gnu.org 2021-02-24 14:20 ` rguenth at gcc dot gnu.org 2021-02-24 14:41 ` rguenth at gcc dot gnu.org 2021-02-24 14:45 ` rguenth at gcc dot gnu.org 2021-02-24 15:09 ` rguenth at gcc dot gnu.org 2021-02-25 10:18 ` rguenth at gcc dot gnu.org 2021-02-25 11:34 ` rguenth at gcc dot gnu.org 2021-02-25 12:09 ` rguenth at gcc dot gnu.org 2021-02-25 12:40 ` rguenth at gcc dot gnu.org 2021-02-25 13:31 ` matz at gcc dot gnu.org 2021-02-25 18:29 ` matz at gcc dot gnu.org 2021-02-25 18:34 ` matz at gcc dot gnu.org 2021-02-26 9:38 ` rguenth at gcc dot gnu.org 2021-03-03 12:16 ` rguenth at gcc dot gnu.org 2021-03-03 14:00 ` matz at gcc dot gnu.org 2021-03-03 14:37 ` rguenth at gcc dot gnu.org 2021-03-03 19:52 ` hubicka 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-99101-4-oyDIywzPqr@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).