public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>
Subject: [PATCH 0/4] Move pass-creation logic into a passes.def file
Date: Thu, 18 Jul 2013 01:18:00 -0000	[thread overview]
Message-ID: <1374110303-9758-1-git-send-email-dmalcolm@redhat.com> (raw)

The following patch series moves the logic for creating the
pipeline of optimization passes out from passes.c and into a new
passes.def file (patches 1 and 2).

It then explicitly numbers those passes that have multiple instances, by
using a NEXT_PASS_NUM macro in place of NEXT_PASS (patch 3)

The motivation for this is subsequent work towards removing global
variables from GCC's internals: by numbering the instances it becomes
possible to create a "class pipeline" and have the fields be declared
via suitable use of passes.def.  See:
http://dmalcolm.fedorapeople.org/gcc/global-state/new-classes.html#pass-classes

The final patch in the sequence adds a script which sanity-checks
passes.def, and prints some stats about the passes.  You can see output
from the script at:

  http://dmalcolm.fedorapeople.org/gcc/2013-07-17/pass-stats.txt

Specifically, it lists single-instanced passes, then all multi-instance
passes, giving the number of instances of each (alphabetically within
each list).

I've successfully bootstrapped and tested the sequence of patches on
x86_64-unknown-linux-gnu: all testcases show the same results as an
unpatched build (relative to r201011).

OK to commit these to trunk?

David Malcolm (4):
  Introduce macros when constructing the tree of passes
  Move the construction of the pass hierarchy into a new passes.def
    file.
  Introduce NEXT_PASS_NUM macro
  Add contrib/check_passes.py script

 contrib/check_passes.py |  58 +++++++
 gcc/Makefile.in         |   2 +-
 gcc/passes.c            | 401 ++---------------------------------------------
 gcc/passes.def          | 406 ++++++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 481 insertions(+), 386 deletions(-)
 create mode 100644 contrib/check_passes.py
 create mode 100644 gcc/passes.def

-- 
1.7.11.7

             reply	other threads:[~2013-07-18  1:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18  1:18 David Malcolm [this message]
2013-07-18  1:18 ` [PATCH 4/4] Add contrib/check_passes.py script David Malcolm
2013-07-18 16:29   ` Jeff Law
2013-07-18  1:18 ` [PATCH 1/4] Introduce macros when constructing the tree of passes David Malcolm
2013-07-18 16:21   ` Jeff Law
2013-07-18 18:33     ` David Malcolm
2013-07-18  1:18 ` [PATCH 2/4] Move the construction of the pass hierarchy into a new passes.def file David Malcolm
2013-07-18 16:25   ` Jakub Jelinek
2013-07-18 16:25   ` Jeff Law
2013-07-18 19:34     ` David Malcolm
2013-07-18  1:32 ` [PATCH 3/4] Introduce NEXT_PASS_NUM macro David Malcolm
2013-07-18  7:10   ` Andrew Pinski
2013-07-18 11:40     ` David Malcolm
2013-07-18 14:58       ` Andrew Pinski
2013-07-29 16:06         ` David Malcolm
2013-07-18 16:03       ` Tom Tromey
2013-07-18 16:25   ` Jeff Law
2013-07-29 19:42     ` David Malcolm
2013-07-29 20:01       ` Jeff Law
2013-07-22 18:45   ` Martin Jambor
2013-07-22 19:36     ` David Malcolm
2013-07-23 15:28       ` Martin Jambor
2013-07-23 15:46         ` David Malcolm
2013-07-24 15:18           ` Martin Jambor
2013-07-18  7:26 ` [PATCH 0/4] Move pass-creation logic into a passes.def file Andrew Pinski

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=1374110303-9758-1-git-send-email-dmalcolm@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@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: 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).