From: Scott Dattalo <scott@dattalo.com>
To: sid@sources.redhat.com
Subject: Profiling: --insn-count=1
Date: Wed, 31 Jul 2002 12:53:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0207311235371.24183-100000@ruckus.brouhaha.com> (raw)
To profile my simulated code, I've been invoking sid like so:
arm-elf-sid --cpu arm --memory-region=0x2020000,0x2000000 \
--memory-region=0xfffe0000,0x1ffff --gdb=2000 --gprof \
--trace-counter --insn-count=1 -EL myprog
I then simulate the application with arm-elf-gcc and examine the results
with arm-elf-gprof.
Now the question I have is there a way to count cpu cycles instead of cpu
instructions? If there was a one-to-one relationship between the two, then
it's not an issue. However, some instructions on the ARM are not
single-cycled. I suppose the real question is, "is there a way to
concisely measure the amount of 'simulated' time it take for a simulation
to run?"
FWIW, I'm using ~6 week old copy of SID.
Scott
next reply other threads:[~2002-07-31 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 12:53 Scott Dattalo [this message]
2002-08-01 4:18 ` Frank Ch. Eigler
2002-08-01 5:03 ` Scott Dattalo
2002-08-01 8:32 ` Frank Ch. Eigler
2002-08-01 9:00 ` Scott Dattalo
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=Pine.LNX.4.44.0207311235371.24183-100000@ruckus.brouhaha.com \
--to=scott@dattalo.com \
--cc=sid@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).