From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24545 invoked by alias); 20 Oct 2011 16:21:20 -0000 Received: (qmail 24370 invoked by uid 22791); 20 Oct 2011 16:21:18 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 20 Oct 2011 16:20:51 +0000 Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id BF6B21B4023; Thu, 20 Oct 2011 16:20:49 +0000 (UTC) From: Mike Frysinger To: Joel Brobecker Subject: Re: GDB / SIM 7.3.1 Cosmetic patch for profile title Date: Thu, 20 Oct 2011 16:35:00 -0000 User-Agent: KMail/1.13.7 (Linux/3.1.0-rc4; KDE/4.6.5; x86_64; ; ) Cc: John Wehle , gdb-patches@sourceware.org References: <201110170428.p9H4SMZO025996@jwlab.FEITH.COM> <201110200017.39834.vapier@gentoo.org> <20111020155918.GG19246@adacore.com> In-Reply-To: <20111020155918.GG19246@adacore.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart9127114.Gat0SGro3E"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201110201220.49954.vapier@gentoo.org> 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: 2011-10/txt/msg00567.txt.bz2 --nextPart9127114.Gat0SGro3E Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-length: 1471 On Thursday 20 October 2011 11:59:18 Joel Brobecker wrote: > > since profile_printf() takes a cpu arg, this fails to build once the > > header printf is pulled out from the loop where "cpu" is declared. >=20 > Ah, correct. A quick look at that function reveals that it only needs > the "cpu" to get access to the associaed PROFILE_FILE. Not sure what > this is and why it is necessary, rather than doing a simple printf. >=20 > In any case, sounded like a good idea, but maybe it wasn't. I'll leave > it to you guys if you want to pursue it. the sim profile code has a --profile-file flag so that you can send the pro= file=20 output to a dedicated file. this is really useful when you're trying to pi= ck=20 apart all the other things the sim may output -- tracing, output from the=20 simulated program itself, etc... when you've got like 4+ different sources= of=20 information sent to one or two fd's, you can see how dedicated file flags a= re a=20 hard necessity :). fundamentally, the profile code operates on a per-cpu basis which makes sen= se=20 in that the execution/profile of each cpu looks very different. and the pr= ofile=20 output code follows this convention. atm, in practice, all output is sent to the same file handle, and most (all= ?)=20 sims i know of only support one cpu. so it's a bit of a wash, but i think = we=20 should stick to supporting the multi-cpu concept everywhere so that future= =20 work is much easier. -mike --nextPart9127114.Gat0SGro3E Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. Content-length: 836 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJOoEphAAoJEEFjO5/oN/WBmpkQAIDDUpThe2DDTVE8/F4HlaZB YdW0BTzIZFrAWf2xldQSJwLTVo3uqBqK67xSHjCGhMrV+qkwf+BsuGsEi1IqFpMS SND+WCs19XBsvP7Ji2sle1lTqGXVbo1vQS0AV8no5/idTdfcU+BxHSQ3xc/bfTDb rGK+jxGr80S08ZU7hxUJbLVf6lAyZJTYLHKRV+6mx4p6z2XBq1IU0+0SltW7TgJF xgZVZhz4zzVl/jBKDLSmrMmflosLUrGmIGfD03u4yO6G7eAg+pO2UNqNLrHI/nIH joyaxKAsNe1UBtLPbeNiBUrkbTz1Uc0ns24v5ZE4F2Kj7meuSRihJujyOmKHtfV7 ax+IKORCkvBJx0cQswOjfMdOW/L87WaEwwHyLeEO9J9+zcIqG9/He95phVoehR8F 0JYYryvKl8TNS1eIfIU3Dp70dfzFTGlwkRVTMEhfhtpgWhzy54mSKvaDRYq0RSOz 7f/gVxQ9HH56spZMYIyAKvA0U6Q28xp14MRofqhDb8KJua1DhUtJdyfW5GWxSukO I+AyobKQYdq8kr6t9/BatmH8/BxNO6FTdTiqYXoU9qJGNidR9FjqLVQSOgqyV2dc 3LzRzJTlX4DWUhiu+CljMPCu8tMrDs4RV2jiBI0QIaAwetvcjQrtxh1BJppNkcZr ZBn5GABizKIS1kUQtIIs =8sPW -----END PGP SIGNATURE----- --nextPart9127114.Gat0SGro3E--