public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Shilin Shakti" <shilins@KPITCummins.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: <cgen@sources.redhat.com>
Subject: RE: Simulator Porting
Date: Wed, 25 May 2005 10:43:00 -0000	[thread overview]
Message-ID: <4A1BE23A7B777442B60F4B4916AE0F1305B2E440@sohm.kpit.com> (raw)

Hi Frank,
Thank you very much for your response.
I had been using the sem-switch.c in the makefile with the '-switch'
option enabled for mloop.in file, similar to the m32r, along with the
'-fast -pbb' options also.
Now i have changed it to use sem.c like you mentioned, with '-scache'
option for mloop.in file (removed -switch, -fast, -pbb options from
makefile for mloop.in).
But I now notice that if i insert a 2 byte 'nop' insn just before the
mov imm insn, that error message doesn't occur and execution seems to be
going on, though i still can't figure if the simulator is correctly
working or not (since our toolchain's printf function is currently
implemented for output to hyperterminal for hardware!!!). Also the
'Program exited normally' message has not come; seems to hang around in
the simulator program itself!

Am i doing all these correctly? Also what do you think might be the
reason for that address alignment issue?

Thanking you once again,
Best Regards,
Shilin

-----Original Message-----
From: Frank Ch. Eigler [mailto:fche@redhat.com]
Sent: Tuesday, May 24, 2005 6:29 PM
To: Shilin Shakti
Cc: cgen@sources.redhat.com
Subject: Re: Simulator Porting


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


---------------------------------
This message contains the information that may be privileged and is  the property of the KPIT Cummins Infosystems LTD.It is intended only for the person to whom it is addressed. If you are not intended recipient, you are not authorized to read, print , retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Cummins does not accept any liability for virus infected mails.

             reply	other threads:[~2005-05-25 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 10:43 Shilin Shakti [this message]
2005-05-25 14:20 ` Frank Ch. Eigler
  -- strict thread matches above, loose matches on Subject: below --
2005-05-26 13:18 Shilin Shakti
2005-05-27 19:04 ` 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=4A1BE23A7B777442B60F4B4916AE0F1305B2E440@sohm.kpit.com \
    --to=shilins@kpitcummins.com \
    --cc=cgen@sources.redhat.com \
    --cc=fche@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).