public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Daniel Berlin <dan@dberlin.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/5738: GCSE missed optimization Date: Wed, 03 Apr 2002 05:06:00 -0000 [thread overview] Message-ID: <20020403130601.11786.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/5738; it has been noted by GNATS. From: Daniel Berlin <dan@dberlin.org> To: rth@gcc.gnu.org, <dann@godzilla.ics.uci.edu>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: optimization/5738: GCSE missed optimization Date: Wed, 3 Apr 2002 07:58:55 -0500 (EST) On 3 Apr 2002 rth@gcc.gnu.org wrote: > Synopsis: GCSE missed optimization > > State-Changed-From-To: open->closed > State-Changed-By: rth > State-Changed-When: Wed Apr 3 02:25:09 2002 > State-Changed-Why: > That's not how partial redundancy elimination (PRE) works. > The object with PRE is to minimize the number of evaluations > of an expression *along a path*. No, the main object of PRE (besides performing GCSE) is to suppress partial redundancies. IE expressions that are available along one or more paths, but missing from some path. It does so by making it fully redundant, copying it to a block (or blocks) such that it reaches all of the paths. It then eliminates the other copies. > There is already one > evaluation along each path, thus PRE considers things > optimal. No it won't. The expression is not in the earliest place possible, and is fully redundant. It *should* copy it to the predecessor, and eliminate the other two copies. > > You want global value numbering or something, which we > don't implement. GVN wouldn't help here, actually. GVN doesn't insert new copies, it only eliminates values that are really still available from some other block. Please don't close this PR, it's correct. --Dan
next reply other threads:[~2002-04-03 13:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-03 5:06 Daniel Berlin [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-15 4:46 bangerth 2002-04-04 8:16 law 2002-04-03 10:55 rth 2002-04-03 10:06 Dan Nicolaescu 2002-04-03 5:36 Daniel Berlin 2002-04-03 2:25 rth 2002-02-20 14:16 dann
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=20020403130601.11786.qmail@sources.redhat.com \ --to=dan@dberlin.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).