From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com, Nick Roberts <nickrob@snap.net.nz>
Subject: Re: [RFC] Fix MI timings
Date: Mon, 09 Mar 2009 21:22:00 -0000 [thread overview]
Message-ID: <20090309212230.GA17609@caradoc.them.org> (raw)
In-Reply-To: <200903100015.03600.vladimir@codesourcery.com>
On Tue, Mar 10, 2009 at 12:15:03AM +0300, Vladimir Prus wrote:
> *This* patch.
You must've been working on programs in some Other Real Language
lately... :-)
> @@ -97,6 +97,8 @@ static void timestamp (struct mi_timestamp *tv);
>
> static void print_diff_now (struct mi_timestamp *start);
> static void print_diff (struct mi_timestamp *start, struct mi_timestamp *end);
> +void print_timing_maybe ();
> +
>
> void
> mi_cmd_gdb_exit (char *command, char **argv, int argc)
Prototypes in .h files only please.
> @@ -1567,6 +1561,15 @@ print_diff_now (struct mi_timestamp *start)
> print_diff (start, &now);
> }
>
> +void
> +print_timing_maybe ()
(void)
> +{
> + // If the command is -enable-timing then do_timings may be
> + // true whilst current_command_ts is not initialized.
/* */
> +void print_timing_maybe ();
(void)
Also, since this is public, please give it an "mi_" prefix.
I have nothing useful to say about the important part of the patch,
though.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-03-09 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 21:10 Vladimir Prus
2009-03-09 21:15 ` Vladimir Prus
2009-03-09 21:22 ` Daniel Jacobowitz [this message]
2009-03-09 21:32 ` Vladimir Prus
2009-03-09 21:36 ` Pedro Alves
2009-03-09 22:07 ` Pedro Alves
2009-03-17 5:27 ` Pedro Alves
2009-03-17 7:26 ` Vladimir Prus
2009-03-17 8:03 ` Vladimir Prus
2009-03-13 7:59 ` Vladimir Prus
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=20090309212230.GA17609@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
--cc=vladimir@codesourcery.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