Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Vermeulen Jan <Jan.Vermeulen@siemens.atea.be>
Cc: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: Re: powerpc simulator questions
Date: Sun, 18 Nov 2001 11:45:00 -0000	[thread overview]
Message-ID: <3C046A8F.1060704@cygnus.com> (raw)
Message-ID: <20011118114500.1-eNwfqb2JdA9PViKnn_15dsy05QMzfa-fKQWdy5IvY@z> (raw)
In-Reply-To: <E76F715C0429D5118F2100508BB9EDEE026135A1@hrtades7.atea.be>

> Hey,
> 
> Thanks for the suggestions.
> It was indeed the memorymap that went haywire. (or the author :)
> 
> I managed to debug/simulate my code. Very nice.
> 
> Just one more question:
> with powerpc-eabi-run, i can see how many cycles have passed for the
> program.
> 
> 1) if I want to know how long it would take on a 200MHz powerpc (and the
> routine takes about 35e6 cycles), then am i correct to use this formula :
> 35e6 cycles / 200e6 Mhz = 175 milliseconds ?
> 
> 2) is the same type of performance measuring in the simulator under gdb?
> for example: breakpoint before a routine, breakpoint after one, and then a
> command "give me number of cycles passed between those 2 breakpoints
> (please)."

I wouldn't take the profile statistics too seriously.  No one ever sat 
down and analized them (Er, there might have been one report to only 
indicate that they were way out :-/).  I should probably delete that 
code (so no one is mis-lead).  It is also known to go into infinite 
loops :-(

Andrew



  reply	other threads:[~2001-11-28  4:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 18:33 Vermeulen Jan
2001-11-27 20:39 ` Andrew Cagney [this message]
2001-11-18 11:45   ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2001-11-01 15:25 Vermeulen Jan
2001-11-01 16:30 ` Andrew Cagney
2001-11-01 16:43 ` Frank Ch. Eigler

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=3C046A8F.1060704@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=Jan.Vermeulen@siemens.atea.be \
    --cc=gdb@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