From: Daniel Jacobowitz <drow@false.org>
To: Janne Hellsten <jjhellst@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: two bugs in the arm simulator
Date: Mon, 04 Jul 2005 15:28:00 -0000 [thread overview]
Message-ID: <20050704152806.GA22129@nevyn.them.org> (raw)
In-Reply-To: <700d600f05070323206be5cb7e@mail.gmail.com>
On Mon, Jul 04, 2005 at 03:20:36PM +0900, Janne Hellsten wrote:
> Hi,
>
> > GNATS ought to have sent you something back. It does have your
> > address. I'm afraid PR 1900 is the least of the problems with the
> > simulator on 64-bit hosts; it appears to be pretty busted. No one is
> > working on either AFAIK though I think there's another PR about the
> > busted simulator somewhere.
>
> Yes, it did send back my reports, but nothing else.
>
> I can probably fix PR 1957 myself, I'd like to get familiar with the
> simulator. The thing is that I'd like to extend GDB's ARM simulator
In that case, you may want to file an FSF copyright assignment.
Otherwise we can't accept substantive contributions.
> so that I can get it to report the number of cycles spent in some
> program. This could be used for simple benchmarking (to detect
> regression over time).
>
> I wonder if such an extension would be a big task? I'm not familiar
> with GDB's code at all.
The GDB simulators aren't even a little bit cycle accurate,
unfortunately.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-04 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 3:06 Janne Hellsten
2005-07-04 3:56 ` Daniel Jacobowitz
2005-07-04 6:20 ` Janne Hellsten
2005-07-04 15:28 ` Daniel Jacobowitz [this message]
2005-07-05 0:07 ` number of executed instructions from simulator (was Re: two bugs in the arm simulator) Janne Hellsten
2005-07-05 8:01 ` two bugs in the arm simulator Janne Hellsten
2005-07-05 13:29 ` Daniel Jacobowitz
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=20050704152806.GA22129@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jjhellst@gmail.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