From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17312 invoked by alias); 22 Jul 2013 18:25:57 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 17293 invoked by uid 89); 22 Jul 2013 18:25:57 -0000 X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_20,KHOP_RCVD_UNTRUST,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE autolearn=no version=3.3.1 Received: from Unknown (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 22 Jul 2013 18:25:57 +0000 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 20EE8A50DE; Mon, 22 Jul 2013 20:25:49 +0200 (CEST) Date: Mon, 22 Jul 2013 18:45:00 -0000 From: Martin Jambor To: David Malcolm Cc: gcc-patches@gcc.gnu.org Subject: Re: [PATCH 3/4] Introduce NEXT_PASS_NUM macro Message-ID: <20130722182548.GB9531@virgil.suse> Mail-Followup-To: David Malcolm , gcc-patches@gcc.gnu.org References: <1374110303-9758-1-git-send-email-dmalcolm@redhat.com> <1374110303-9758-4-git-send-email-dmalcolm@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1374110303-9758-4-git-send-email-dmalcolm@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-07/txt/msg00945.txt.bz2 Hi, On Wed, Jul 17, 2013 at 09:18:22PM -0400, David Malcolm wrote: > gcc/ > > 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). > I don't really understand what you want to achieve. Are you sure the benefits are worth the work necessary to implement the processing of passes.def.in? Especially given that we already initialize static_pass_number at run time and copy stuff around in make_pass_instance when it is already set. I assume this would somehow allow us to directly dump data of say forwprop3 as apposed to forwprop2 to but that would require constant awareness of the sequence number of the currently running pass, which I think is also unpleasant and error-prone. I mean, you may have perfectly legitimate reasons for doing this, I'm just wondering whether we are perhaps over-engineering this a bit. Thanks, Martin