From: Jeff Law <law@redhat.com>
To: Tom de Vries <Tom_deVries@mentor.com>,
"gcc-patches@gnu.org" <gcc-patches@gnu.org>
Subject: Re: [PATCH] Add pass parameter to TERMINATE_PASS_LIST
Date: Fri, 11 Dec 2015 20:27:00 -0000 [thread overview]
Message-ID: <566B318F.9060304@redhat.com> (raw)
In-Reply-To: <566AAC96.2020304@mentor.com>
On 12/11/2015 03:59 AM, Tom de Vries wrote:
> Hi,
>
> This patch adds a parameter to TERMINATE_PASS_LIST, that should match
> the pass list it's supposed to terminate.
>
> The intention of the patch is that it:
> - makes it easier to understand the top-level hierarchy of the pass
> list (given that the top-level list may be quite long).
> - ensures that INSERT_PASSES_AFTER and TERMINATE_PASS_LIST are paired.
>
> OK for stage3/stage1 trunk, if bootstrap and reg-test succeeds?
I'd prefer to wait for stage1 on this. It feels like we've got way too
much macro-magic going on in here. I guess as long as we have the
macro-magic in here, verification like this is OK.
Jeff
prev parent reply other threads:[~2015-12-11 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 10:59 Tom de Vries
2015-12-11 20:27 ` Jeff Law [this message]
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=566B318F.9060304@redhat.com \
--to=law@redhat.com \
--cc=Tom_deVries@mentor.com \
--cc=gcc-patches@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).