From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: jbeniston@compxs.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Output execution stats from ARM simulator
Date: Mon, 29 Nov 2004 14:47:00 -0000 [thread overview]
Message-ID: <1101739601.1585.44.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <001d01c4d620$edbb9e50$0bbda8c0@Kindrogan>
On Mon, 2004-11-29 at 14:37, Jon Beniston wrote:
> Hi,
>
> The attached patch outputs the number of instructions executed and the
> number of cycles taken by the ARM simulator.
>
> Cheers,
> Jon
>
> 2004-11-29 Jon Beniston <jon@beniston.com>
>
> * wrapper.c (sim_info): Output number of instructions
> executed and number of cycles taken to execute them.
While I don't see anything wrong with your patch, I'm not sure whether
that information is accurately tracked any more. So the numbers
probably aren't meaningful, especially for any core other than an ARM7
(and I don't mean an ARM7TDMI either).
R.
next prev parent reply other threads:[~2004-11-29 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 14:39 Jon Beniston
2004-11-29 14:47 ` Richard Earnshaw [this message]
2004-11-29 14:57 ` Jon Beniston
2004-11-29 15:06 ` Richard Earnshaw
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=1101739601.1585.44.camel@pc960.cambridge.arm.com \
--to=rearnsha@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jbeniston@compxs.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