This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH 3/4] Introduce NEXT_PASS_NUM macro
- From: Jeff Law <law at redhat dot com>
- To: David Malcolm <dmalcolm at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Thu, 18 Jul 2013 10:25:18 -0600
- Subject: Re: [PATCH 3/4] Introduce NEXT_PASS_NUM macro
- References: <1374110303-9758-1-git-send-email-dmalcolm at redhat dot com> <1374110303-9758-4-git-send-email-dmalcolm at redhat dot com>
On 07/17/2013 07:18 PM, David Malcolm wrote:
So this means we have to track down the instance number if we add a
duplicate pass in the pipeline. I can see positives and negatives of
doing that. I'll go along as I'm a proponent of the goal of having the
passes be a first class object.
Explicitly number the instances of passes within passes.def.
This is needed by a subsequent patch so that we can create
fields within the pipeline class for each pass instance (to help
locate pass instances when debugging).
* passes.c (NEXT_PASS_NUM): Define.
* passes.def (NEXT_PASS, NEXT_PASS_NUM): Replace uses of
NEXT_PASS on passes that have multiple instances with uses of
Ok for the trunk.