From: "Frank Ch. Eigler" <fche@redhat.com>
To: Shilin Shakti <shilins@KPITCummins.com>
Cc: cgen@sources.redhat.com
Subject: Re: Simulator Porting
Date: Tue, 24 May 2005 12:59:00 -0000 [thread overview]
Message-ID: <20050524125904.GB10919@redhat.com> (raw)
In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F1305AD34ED@sohm.kpit.com>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Hi -
On Tue, May 24, 2005 at 12:26:48PM +0530, Shilin Shakti wrote:
> [...]
> following message:
> "2 byte write to unmapped address 0xfffffffe at 0x404",=20
> while the similar m32r program runs fine. At 0x404 is a move immediate da
> ta instruction in my case (but how this 0xfffffffe address i'm confused!!
> ).
You could run the simulator under gdb, and put a breakpoint at the
point in the generated sem.c file which executes that move-immediate
instruction. Without posting more information, such as your modified
.cpu file and disassembled sample program, we won't be able to help
much.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-24 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 6:58 Shilin Shakti
2005-05-24 12:59 ` Frank Ch. Eigler [this message]
2005-05-24 7:31 Shilin Shakti
2005-05-25 10:43 Shilin Shakti
2005-05-25 14:20 ` Frank Ch. Eigler
2005-05-26 13:18 Shilin Shakti
2005-05-27 19:04 ` 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=20050524125904.GB10919@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).