public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chrbr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54546] SH: Enable -fshrink-wrap Date: Thu, 13 Sep 2012 06:41:00 -0000 [thread overview] Message-ID: <bug-54546-4-F7YeJ1xNxY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54546-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54546 --- Comment #1 from chrbr at gcc dot gnu.org 2012-09-13 06:40:54 UTC --- shrink-wrapping exposes a few problems related to partitioning. 1) Tries to duplicate a Basic block that has only one predecessor coming from a different partition. Since the edge is not marking with with EDGE_CROSSING missing across section boundary. Note that even with EDGE_CROSSING information, the generated code would be quite bad, with extra jumps coming from the critical path. The problem is explained with the start of a resolution here http://gcc.gnu.org/ml/gcc-patches/2012-09/msg00794.html 2) Seem to miss redirecting CROSS_JUMPING jumps. When we have jump_insn 205 204 179 4 (set (pc) (reg:SI 1 r1 [237])) 316 {indirect_jump_compact} (expr_list:REG_CROSSING_JUMP (nil) (nil)) we have a JUMP_LABEL (insn) containing the setting or r1 with the label_rtx, but 'patch_jump_insn' fails to see it, although it looks like the branch could be redirected.
next prev parent reply other threads:[~2012-09-13 6:41 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-11 8:45 [Bug target/54546] New: " chrbr at gcc dot gnu.org 2012-09-11 8:46 ` [Bug target/54546] " chrbr at gcc dot gnu.org 2012-09-13 6:41 ` chrbr at gcc dot gnu.org [this message] 2012-09-14 13:22 ` chrbr at gcc dot gnu.org 2012-11-01 0:03 ` olegendo at gcc dot gnu.org 2012-11-07 13:24 ` chrbr at gcc dot gnu.org 2012-11-09 14:40 ` chrbr 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-54546-4-F7YeJ1xNxY@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).