public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "makhaloff at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/57940] New: [PATCH] Rerun df_analyze after delete_unmarked_insns during DCE Date: Sat, 20 Jul 2013 09:29:00 -0000 [thread overview] Message-ID: <bug-57940-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57940 Bug ID: 57940 Summary: [PATCH] Rerun df_analyze after delete_unmarked_insns during DCE Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: makhaloff at gmail dot com Hello! If delete_unmarked_insns deletes some insn, DF state might be out of date, and, regs_ever_live might contain unused registers till the end. Fixed by forcing regs_ever_live update and rerunning df_analyze () at fini_dce(). I found this bug on my target (not included into main sources). But I can send everything you need to reproduce this bug. Using gcc-4.8.1 2013-07-20 Alexey Makhalov <makhaloff@gmail.com> * dce.c (fini_dce): Call df_analyze again just in case delete_unmarked_insns removed anything. --- dce.c (revision 361) +++ dce.c (working copy) @@ -745,6 +745,12 @@ bitmap_obstack_release (&dce_blocks_bitmap_obstack); bitmap_obstack_release (&dce_tmp_bitmap_obstack); } + + if (!df_in_progress) + { + df_compute_regs_ever_live (true); + df_analyze (); + } }
next reply other threads:[~2013-07-20 9:29 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-20 9:29 makhaloff at gmail dot com [this message] 2014-02-22 8:51 ` [Bug rtl-optimization/57940] " ebotcazou 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-57940-4@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).