From: Nathan Froyd <froydnj@codesourcery.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] add statistics counting to postreload, copy-rename, and math-opts
Date: Tue, 12 Apr 2011 14:51:00 -0000 [thread overview]
Message-ID: <20110412145143.GH23480@codesourcery.com> (raw)
In-Reply-To: <BANLkTi=OfUfbFr7yGN-ibb8GYc0QdjN1+w@mail.gmail.com>
On Tue, Apr 12, 2011 at 04:37:42PM +0200, Richard Guenther wrote:
> On Tue, Apr 12, 2011 at 4:32 PM, Nathan Froyd <froydnj@codesourcery.com> wrote:
> > Thanks. Â I may go twiddle that patch to do something similar to mine and
> > submit that. Â Do you use your patch for checking that the same set of
> > optimizations get performed, then? Â I'm interested in using the
> > statistics for identifying passes that don't buy us much across a wide
> > variety of codebases. Â (Suggestions for suitable ones welcome!)
>
> Yes, I used it exactly for that. And also to verify that passes don't
> do anything if replicated (well, for those that shouldn't at least).
>
> Don't expect any low-hanging fruit though ;) I catched all of it already.
>
> Candidates are obviously SPEC and GCC itself. I also use tramp3d
> of course. That said, even if a pass does nearly nothing we often
> have testcases that need it ...
True, but maybe those testcases should be adjusted--per-pass flags,
rather than blindly assuming -O2 includes them. And it's not clear to
me that the statistics_counter_event infrastructure really helps
catching do-nothing passes, since it doesn't record stats that increment
by zero...
-Nathan
next prev parent reply other threads:[~2011-04-12 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 14:16 Nathan Froyd
2011-04-12 14:27 ` Richard Guenther
2011-04-12 14:32 ` Nathan Froyd
2011-04-12 14:38 ` Richard Guenther
2011-04-12 14:51 ` Nathan Froyd [this message]
2011-04-12 14:54 ` Richard Guenther
2011-04-12 15:09 ` Nathan Froyd
2011-04-13 9:07 ` Richard Guenther
2011-04-13 18:43 ` Nathan Froyd
2011-04-14 8:51 ` Richard Guenther
2011-04-12 15:01 ` Steven Bosscher
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=20110412145143.GH23480@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).