public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jskumari at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/109009] Shrink Wrap missed opportunity Date: Sun, 05 Mar 2023 05:23:43 +0000 [thread overview] Message-ID: <bug-109009-4-Se3Rr1lN60@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109009-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109009 --- Comment #2 from Surya Kumari Jangala <jskumari at gcc dot gnu.org> --- For the working testcase: long foo (long i, long cond) { if (cond) bar (); return i; } The input RTL to the shrink wrap pass is: BB2: set r100, compare(r4, 0) if r100 jump BB4 else jump BB3 BB3: set mem(r1+32), r3 call bar() set r3, mem(r1+32) BB4: return r3 The shrink wrap pass concludes that only BB3 requires a prolog and successfully does shrink wrapping. For the non-working case: long foo (long i, long cond) { if (cond) bar (); return i+1; } The input rtl to the shrink wrap pass is: BB2: set r100, compare(r4, 0) set r31, r3 if r100 jump BB4 else jump BB3 BB3: call bar() BB4: set r3, r31+1 return r3 The shrink wrap pass decides that both BB2 and BB3 require a prolog, and finally the prolog is placed in BB2. Thus shrink wrapping fails for this test.
next prev parent reply other threads:[~2023-03-05 5:23 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-03 14:04 [Bug rtl-optimization/109009] New: " jskumari at gcc dot gnu.org 2023-03-03 16:40 ` [Bug rtl-optimization/109009] " segher at gcc dot gnu.org 2023-03-05 5:23 ` jskumari at gcc dot gnu.org [this message] 2023-03-05 12:19 ` jskumari at gcc dot gnu.org 2023-03-05 15:01 ` segher at gcc dot gnu.org 2023-04-14 17:44 ` jskumari at gcc dot gnu.org 2023-05-10 11:51 ` jskumari at gcc dot gnu.org 2023-05-11 9:49 ` jskumari at gcc dot gnu.org 2023-06-23 15:03 ` jskumari at gcc dot gnu.org 2023-06-23 19:57 ` bergner at gcc dot gnu.org 2023-06-23 20:04 ` bergner at gcc dot gnu.org 2023-06-27 13:18 ` jskumari at gcc dot gnu.org 2023-06-27 13:19 ` jskumari 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-109009-4-Se3Rr1lN60@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).