This is the mail archive of the
sid@sources.redhat.com
mailing list for the SID project.
Profiling: --insn-count=1
- From: Scott Dattalo <scott at dattalo dot com>
- To: sid at sources dot redhat dot com
- Date: Wed, 31 Jul 2002 12:53:37 -0700 (PDT)
- Subject: Profiling: --insn-count=1
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