From: "Frank Ch. Eigler" <fche@redhat.com>
To: Shilin Shakti <shilins@KPITCummins.com>
Cc: cgen@sources.redhat.com
Subject: Re: Simulator Porting
Date: Fri, 27 May 2005 19:04:00 -0000 [thread overview]
Message-ID: <20050527190350.GG9705@redhat.com> (raw)
In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F1305BD192E@sohm.kpit.com>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
Hi -
On Thu, May 26, 2005 at 06:41:37PM +0530, Shilin Shakti wrote:
> [...]
> Regarding enabling the sim tracing option, i have done it in the
> 'configure' file (--enable-sim-trace option i guess).
That, plus use "(gdb) target sim OPTIONS" where OPTIONS includes
actual activation (not just capability) instructions like
"--trace-insn". See sim/common/*trace*.
> But by the gdb-linked variant of the simulator did you mean the
> 'step' option to be passed that is checked in 'main' (mentioned in
> \sim\common\nrun.c) for single stepping?
I meant "(gdb) target sim; load; stepi; stepi; stepi; ...", so that
the sim is made to execute one target instruction at a time.
> I could not fully comprehend this option also. [...]
I suggest building a vanilla working cross toolchain first, learning
how to use all the tools, and only after that attempting to port them.
It will take far too long to explain both usage and porting in email.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-27 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 13:18 Shilin Shakti
2005-05-27 19:04 ` Frank Ch. Eigler [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-25 10:43 Shilin Shakti
2005-05-25 14:20 ` Frank Ch. Eigler
2005-05-24 7:31 Shilin Shakti
2005-05-24 6:58 Shilin Shakti
2005-05-24 12:59 ` 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=20050527190350.GG9705@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=shilins@KPITCummins.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).