From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2362 invoked by alias); 8 Mar 2011 21:08:08 -0000 Received: (qmail 2352 invoked by uid 22791); 8 Mar 2011 21:08:07 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-ww0-f51.google.com (HELO mail-ww0-f51.google.com) (74.125.82.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 08 Mar 2011 21:08:01 +0000 Received: by wwj40 with SMTP id 40so1393509wwj.8 for ; Tue, 08 Mar 2011 13:07:59 -0800 (PST) Received: by 10.216.209.230 with SMTP id s80mr4891508weo.26.1299618478942; Tue, 08 Mar 2011 13:07:58 -0800 (PST) Received: from [192.168.2.99] (cpc2-cmbg8-0-0-cust61.5-4.cable.virginmedia.com [82.6.108.62]) by mx.google.com with ESMTPS id g8sm525017wej.23.2011.03.08.13.07.56 (version=SSLv3 cipher=OTHER); Tue, 08 Mar 2011 13:07:57 -0800 (PST) Message-ID: <4D769A9B.7060704@gmail.com> Date: Tue, 08 Mar 2011 21:08:00 -0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Basile Starynkevitch CC: gcc@gcc.gnu.org Subject: Re: debug & trace printing from GCC plugins (& MELT extensions) References: <20110307163958.85f23bdd.basile@starynkevitch.net> In-Reply-To: <20110307163958.85f23bdd.basile@starynkevitch.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2011-03/txt/msg00097.txt.bz2 On 07/03/2011 15:39, Basile Starynkevitch wrote: > So please accept (at least temporily) the usefulness of debug & trace > printing. > > My question then is how to implement it nicely? > And I don't know if debug printing should go to stdout or to stderr. MELT is for writing new passes, right? So it could use the existing per-pass dump files mechanism I would expect. cheers, DaveK