From: Mike Frysinger <vapier@gentoo.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: John Wehle <john@feith.com>, gdb-patches@sourceware.org
Subject: Re: GDB / SIM 7.3.1 Cosmetic patch for profile title
Date: Thu, 20 Oct 2011 09:26:00 -0000 [thread overview]
Message-ID: <201110200017.39834.vapier@gentoo.org> (raw)
In-Reply-To: <20111019010522.GE19246@adacore.com>
[-- Attachment #1: Type: Text/Plain, Size: 1204 bytes --]
On Tuesday 18 October 2011 21:05:22 Joel Brobecker wrote:
> > As a side note, it took me a while to understand some of the logic.
> > It looks like `print_title_p' really means `we-have-some-profile-data'.
> >
> > So, if it was me, [...]
>
> In fact, here is what I meant. If someone can test it and confirm
> that I didn't screw something up, we could commit that. I think
> it's a lot clearer this way, no?
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.
i think the intention might have been for the header to be printed once per
cpu since the output log file exists per cpu. so if you want to pull out the
inner loop into like sim_cpu_has_profile_data (SIM_DESC sd, sim_cpu *cpu), that
would probably work, but we'd still want the outer loop that walks all the
cpu's in the profile_info() func. maybe we can merge that loop with the cpu
loop right below ...
> --- a/sim/common/sim-profile.c
> +++ b/sim/common/sim-profile.c
>
> + /* No profile data found. Return zero. */
> + return 0;
> +
> +}
don't think you want that blank line before the closing brace
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-10-20 4:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 7:13 John Wehle
2011-10-17 16:00 ` Mike Frysinger
2011-10-19 1:05 ` Joel Brobecker
2011-10-19 2:08 ` Joel Brobecker
2011-10-20 9:26 ` Mike Frysinger [this message]
2011-10-20 16:21 ` Joel Brobecker
2011-10-20 16:35 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201110200017.39834.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=john@feith.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox