public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/34503] Issues with constant/copy propagation implementation in gcse.c Date: Mon, 17 Dec 2007 08:31:00 -0000 [thread overview] Message-ID: <20071217083050.28832.qmail@sourceware.org> (raw) In-Reply-To: <bug-34503-280@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from steven at gcc dot gnu dot org 2007-12-17 08:30 ------- The global pass uses inefficient local dataflow properties. Because there is a local cprop pass before the global one, some constants/copies do not have to be recorded. This results in a smaller set of expressions to compute AVAIL for. Some experiments I did, showed that the set can be reduced by more than an order of magnitude for large functions (for example try the idea on c-common.c). A register R in defined a load-immediate instruction (i.e. R<-const) in basic block B should not be recorded if the register is not in LIVE_OUT(B)After local cprop, the constant is propagated as far as possible within B, and the definition of R does not reach any uses outside B. Thus, not recording the register value cannot result in missed optimizations. Likewise, if R1 is defined in a copy instruction R1<-R2 in basic block B, and R1 is not in LIVE_OUT(B), and R2 is also not in LIVE_OUT(B), then recording the copy cannot result in missed optimizations, because R2 will have been propagated locally as far as possible already. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34503
next prev parent reply other threads:[~2007-12-17 8:31 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-12-17 8:17 [Bug rtl-optimization/34503] New: " steven at gcc dot gnu dot org 2007-12-17 8:20 ` [Bug rtl-optimization/34503] " steven at gcc dot gnu dot org 2007-12-17 8:22 ` steven at gcc dot gnu dot org 2007-12-17 8:31 ` steven at gcc dot gnu dot org [this message] 2007-12-17 8:38 ` steven at gcc dot gnu dot org 2007-12-17 8:41 ` steven at gcc dot gnu dot org 2007-12-17 8:42 ` steven at gcc dot gnu dot org 2008-05-24 14:32 ` steven at gcc dot gnu dot org 2010-02-12 22:00 ` steven at gcc dot gnu dot org [not found] <bug-34503-4@http.gcc.gnu.org/bugzilla/> 2015-03-24 10:29 ` steven at gcc dot gnu.org 2015-04-24 4:50 ` thopre01 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=20071217083050.28832.qmail@sourceware.org \ --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).