From: Andrew Pinski <pinskia@physics.uc.edu>
To: jimbob@google.com
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fold more aggressively for trip counts
Date: Wed, 03 Jan 2007 02:50:00 -0000 [thread overview]
Message-ID: <200701030251.l032pFue004359@localhost.localdomain> (raw)
In-Reply-To: <17819.5994.111024.985123@whippen.corp.google.com>
>
> Attached is a patch to do a little bit of extra work in analyzing trip
> counts for loops. As a side benefit, some other phases will perhaps
> get slightly better folding results.
>
> The motivation for this patch came from some experiments I did with
> doing strength reduction and linear function test replacement rather
> early in optimization, before, e.g., vectorization. At first, code
> introduced by SR caused some failures by keeping loops from being
> analyzed well, hence the genesis of this patch.
>
> Bootstrapped and tested on i686-pc-linux-gnu.
>
> -- Robert Kennedy
>
> ------------------------------
>
> + /* Did somebody make sure te is canonicalized somehow? What are the
^
Add h there.
> + rules for its canonicalization? */
The rules for canonicalization should be documented in c-tree.texi but they
are not :(. Right now maybe_canonicalize_comparison documents the,.
Thanks,
Andrew Pinski
next prev parent reply other threads:[~2007-01-03 2:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 2:40 Robert Kennedy
2007-01-03 2:50 ` Andrew Pinski [this message]
2007-01-03 8:49 ` Paolo Bonzini
2007-01-03 13:57 ` Richard Guenther
2007-01-03 15:14 ` Daniel Berlin
2007-01-04 19:35 ` Robert Kennedy
2007-01-04 19:46 ` Richard Guenther
2007-01-04 19:49 ` Robert Kennedy
2007-01-04 19:54 ` Richard Guenther
2007-01-04 19:58 ` Robert Kennedy
2007-01-04 22:59 ` Zdenek Dvorak
2007-01-05 1:18 ` Robert Kennedy
2007-01-05 7:46 ` Zdenek Dvorak
2007-01-05 19:08 ` Robert Kennedy
2007-01-10 0:05 ` Robert Kennedy
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=200701030251.l032pFue004359@localhost.localdomain \
--to=pinskia@physics.uc.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimbob@google.com \
/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: link
Be 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).