public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104038] ranger infinite loop on a PHI statement Date: Fri, 14 Jan 2022 22:17:22 +0000 [thread overview] Message-ID: <bug-104038-4-GFixJTOgRm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104038-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104038 --- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> --- The problem is reproducible with -O1 and above. To confirm it's not infinite recursion I let the process run for about an hour before killing it. Memory consumption seems to slowly but steadily increase as GCC spins.
next prev parent reply other threads:[~2022-01-14 22:17 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-14 21:58 [Bug tree-optimization/104038] New: " msebor at gcc dot gnu.org 2022-01-14 22:00 ` [Bug tree-optimization/104038] " msebor at gcc dot gnu.org 2022-01-14 22:02 ` msebor at gcc dot gnu.org 2022-01-14 22:07 ` msebor at gcc dot gnu.org 2022-01-14 22:17 ` msebor at gcc dot gnu.org [this message] 2022-01-15 0:13 ` pinskia at gcc dot gnu.org 2022-01-15 0:13 ` pinskia at gcc dot gnu.org 2022-01-16 0:03 ` [Bug tree-optimization/104038] ranger infinite loop on a PHI statement while building Clang msebor at gcc dot gnu.org 2022-01-16 15:57 ` amacleod at redhat dot com 2022-01-18 15:31 ` cvs-commit at gcc dot gnu.org 2022-01-18 15:32 ` amacleod at redhat 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-104038-4-GFixJTOgRm@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).