public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/110528] selective scheduling seems to go into an infinite loop Date: Tue, 04 Jul 2023 00:23:27 +0000 [thread overview] Message-ID: <bug-110528-4-AKZCpsPMAP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110528-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110528 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Here is a testcase which does not go into an infinite loop but takes a little more than 4 seconds to compile which is a lot: ``` static unsigned short g_231 = 1UL; void func_61(unsigned p_62) { unsigned char g_116 = 0xE3L; int l_733; int l_661; unsigned char l_746; for (l_733 = 5; (l_733 >= 1); l_733 -= 1) for (l_746 = 1; (l_746 <= 7); l_746 += 1) for (g_116 = 2; (g_116 <= 7); g_116 += 1) for (l_661 = 6; (l_661 >= 0); l_661 -= 1) { &g_231; (g_231) = (0x84EAL <= p_62); } } ``` This is with `-gstatement-frontiers -O3 -fselective-scheduling2`. Without `-fselective-scheduling2` GCC compiles this less than a second.
next prev parent reply other threads:[~2023-07-04 0:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-03 5:47 [Bug c/110528] New: Timeout with with specific optimizations 19373742 at buaa dot edu.cn 2023-07-03 5:48 ` [Bug c/110528] " 19373742 at buaa dot edu.cn 2023-07-03 5:58 ` [Bug middle-end/110528] " pinskia at gcc dot gnu.org 2023-07-03 7:16 ` rguenth at gcc dot gnu.org 2023-07-03 8:37 ` 19373742 at buaa dot edu.cn 2023-07-03 8:42 ` pinskia at gcc dot gnu.org 2023-07-03 22:04 ` [Bug rtl-optimization/110528] selective scheduling seems to go into an infinite loop pinskia at gcc dot gnu.org 2023-07-04 0:23 ` pinskia at gcc dot gnu.org [this message] 2023-07-04 0:29 ` pinskia at gcc dot gnu.org 2024-02-19 13:58 ` 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-110528-4-AKZCpsPMAP@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).