public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60520] stack adjustment are not merged anymore Date: Fri, 14 Mar 2014 05:14:00 -0000 [thread overview] Message-ID: <bug-60520-4-eu3alGtGvM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60520-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60520 --- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> --- This change: diff --git a/gcc/function.c b/gcc/function.c index a61e475..3b6718f 100644 --- a/gcc/function.c +++ b/gcc/function.c @@ -6238,6 +6238,7 @@ thread_prologue_and_epilogue_insns (void) } /* Now duplicate the tails. */ if (!bitmap_empty_p (&bb_tail)) + { FOR_EACH_BB_REVERSE_FN (bb, cfun) { basic_block copy_bb, tbb; @@ -6304,6 +6305,17 @@ thread_prologue_and_epilogue_insns (void) if (bitmap_empty_p (&bb_tail)) break; } + + /* Basic blocks may have been changed. Merge each basic block + with its successor if possible. */ + FOR_EACH_BB_FN (bb, cfun) + if (single_succ_p (bb)) + { + basic_block succ_bb = single_succ (bb); + if (can_merge_blocks_p (bb, succ_bb)) + merge_blocks (bb, succ_bb); + } + } } fail_shrinkwrap: seems to work.
next prev parent reply other threads:[~2014-03-14 5:14 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-13 21:26 [Bug target/60520] New: " ubizjak at gmail dot com 2014-03-13 21:41 ` [Bug target/60520] " hjl.tools at gmail dot com 2014-03-13 22:02 ` hjl.tools at gmail dot com 2014-03-13 22:22 ` hjl.tools at gmail dot com 2014-03-14 5:14 ` hjl.tools at gmail dot com [this message] 2014-03-14 8:03 ` rguenth at gcc dot gnu.org 2014-03-14 8:27 ` jakub at gcc dot gnu.org 2014-03-14 8:49 ` ubizjak at gmail dot com 2014-03-14 8:59 ` ubizjak at gmail dot com 2014-03-14 15:45 ` hjl.tools at gmail dot com 2014-03-14 16:20 ` jakub at gcc dot gnu.org 2014-03-14 20:33 ` hjl.tools at gmail dot com 2014-03-19 21:56 ` hjl.tools at gmail 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-60520-4-eu3alGtGvM@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).