From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28681 invoked by alias); 1 Jan 2007 16:21:55 -0000 Received: (qmail 28673 invoked by uid 22791); 1 Jan 2007 16:21:55 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Mon, 01 Jan 2007 16:21:50 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1H1Puz-0003Xc-Uv; Mon, 01 Jan 2007 11:21:46 -0500 Date: Mon, 01 Jan 2007 16:21:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: Eli Zaretskii , gdb-patches@sourceware.org Subject: Re: [PATCH] MI: new timing command Message-ID: <20070101162143.GB13508@nevyn.them.org> Mail-Followup-To: Nick Roberts , Eli Zaretskii , gdb-patches@sourceware.org References: <17814.10139.269708.848818@kahikatea.snap.net.nz> <17814.58031.865155.682869@kahikatea.snap.net.nz> <20061231042547.GA3236@nevyn.them.org> <17815.18190.987950.612053@kahikatea.snap.net.nz> <20061231054946.GA4873@nevyn.them.org> <17815.27092.497145.908734@kahikatea.snap.net.nz> <20061231151527.GC16449@nevyn.them.org> <17816.53619.895367.798678@farnswood.snap.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17816.53619.895367.798678@farnswood.snap.net.nz> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-01/txt/msg00024.txt.bz2 On Mon, Jan 01, 2007 at 10:16:35PM +1300, Nick Roberts wrote: > I wasn't aware of "maint time 1" which does indeed seem very similar. In that > case don't understand why you suggested "-gdb-set mi profiling on" and not > "-gdb-set mi set time on". Indeed, it was a mistake on my part. > Anyway, in the case of MI, I'm not sure that you > would want the user to be able to turn it on, so I'm not sure that the same > setting is a good idea. Initially I would just use it manually from the > command line. I don't currently have a front end that can consume the output > but it clearly makes sense for the future. It's just a new field in various outputs; shouldn't a properly written MI parser ignore them? Anyway, it might not be wise to make it easy for end users to enable it, indeed. That's a good reason to use -enable-timings as you/Apple did. -- Daniel Jacobowitz CodeSourcery