public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97627] [9/10/11 Regression] loop end condition missing - endless loop with -fPIC Date: Mon, 25 Jan 2021 11:32:00 +0000 [thread overview] Message-ID: <bug-97627-4-90B839GhOt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97627-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97627 --- Comment #12 from bin cheng <amker at gcc dot gnu.org> --- a. why the loop is considered as infinite b. we need to skip fake exit edges in niter analysis?
next prev parent reply other threads:[~2021-01-25 11:32 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-29 11:32 [Bug c++/97627] New: loop end condition missing - endless loop marcin.jachu19 at gmail dot com 2020-10-29 12:19 ` [Bug c++/97627] [9/10/11 Regression] loop end condition missing - endless loop with -fPIC rguenth at gcc dot gnu.org 2020-10-29 12:21 ` jakub at gcc dot gnu.org 2020-10-29 12:26 ` jakub at gcc dot gnu.org 2020-10-29 12:32 ` jakub at gcc dot gnu.org 2020-10-29 12:56 ` amker at gcc dot gnu.org 2020-10-30 11:29 ` rguenth at gcc dot gnu.org 2020-11-03 13:14 ` rguenth at gcc dot gnu.org 2020-11-03 13:15 ` rguenth at gcc dot gnu.org 2021-01-21 12:07 ` jakub at gcc dot gnu.org 2021-01-21 12:24 ` amker at gcc dot gnu.org 2021-01-25 11:19 ` amker at gcc dot gnu.org 2021-01-25 11:29 ` amker at gcc dot gnu.org 2021-01-25 11:32 ` amker at gcc dot gnu.org [this message] 2021-01-29 11:01 ` [Bug tree-optimization/97627] " cvs-commit at gcc dot gnu.org 2021-01-29 11:08 ` [Bug tree-optimization/97627] [9 " rguenth at gcc dot gnu.org 2021-01-29 11:09 ` cvs-commit at gcc dot gnu.org 2021-01-29 11:51 ` cvs-commit at gcc dot gnu.org 2021-01-29 11:51 ` 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-97627-4-90B839GhOt@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).