From: Tom Tromey <tromey@redhat.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Andrew Pinski <pinskia@gmail.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 3/4] Introduce NEXT_PASS_NUM macro
Date: Thu, 18 Jul 2013 16:03:00 -0000 [thread overview]
Message-ID: <874nbrdhtj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1374147182.31223.28.camel@surprise> (David Malcolm's message of "Thu, 18 Jul 2013 07:33:02 -0400")
>>>>> "David" == David Malcolm <dmalcolm@redhat.com> writes:
David> If so, what tools are blessed for usage at build time? (I'd prefer
David> Python, but I don't think that's a build-time dep yet).
http://www.gnu.org/prep/standards/html_node/Utilities-in-Makefiles.html#Utilities-in-Makefiles
Tom
next prev parent reply other threads:[~2013-07-18 15:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 1:18 [PATCH 0/4] Move pass-creation logic into a passes.def file David Malcolm
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 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: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: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 [this message]
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=874nbrdhtj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@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).