Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Mark and Janice Juszczec" <juszczec@hotmail.com>
To: kevink@mips.com, linux-mips@linux-mips.org
Cc: uhler@mips.com, dom@mips.com, echristo@redhat.com
Subject: Re: r3000 instruction set
Date: Mon, 23 Feb 2004 20:48:39 +0000	[thread overview]
Message-ID: <Law10-F10138dWMJ69i0000d0f4@hotmail.com> (raw)


Kevin

Its been a few weeks since I built this version of kaffe.  The configure 
output says I did specify --with-engine=intrp.  I'll delete the compiled 
stuff, reconfigure (double checking that I give it --with-engine=intrp), 
recompile and retest.

I'll post my results.

Mark



>From: "Kevin D. Kissell" <kevink@mips.com>
>To: "Mark and Janice Juszczec" <juszczec@hotmail.com>,        
><linux-mips@linux-mips.org>
>CC: <uhler@mips.com>, <dom@mips.com>, <echristo@redhat.com>
>Subject: Re: r3000 instruction set
>Date: Mon, 23 Feb 2004 18:21:19 +0100
>
> > Someone suggested posting the message I get.  Here it is:
> >
> > >./kaffe-bin FirstClass
> > [kaffe-bin:6] Illgal instruction 674696a at 2abb034, ra=2adbffd0,
> > P0_STATUS=0000500
> > pid 6: killed (signal 4)
> > >Reading command line: Try again
> > Kernel panic: Attmpted to kill int!
>
>Let me guess.  You are running little-endian.  The instruction word
>in memory would be 0x6a697406.  Do you think it's a coincidence
>that 0x6a6974 spells "jit" in ASCII?  ;o)
>
>The reported address range looks like that where kaffe builds its
>JITted instruciton buffers in MIPS/Linux.  And, like I say, JIT is
>somewhat broken for MIPS in Kaffe.  Which version of the kaffe sources
>are you building, and have you tried configuring with --with-engine=intrp
>as I suggested?
>
>             Regards,
>
>             Kevin K.

_________________________________________________________________
Click, drag and drop. My MSN is the simple way to design your homepage. 
http://click.atdmt.com/AVE/go/onm00200364ave/direct/01/

             reply	other threads:[~2004-02-23 20:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 20:48 Mark and Janice Juszczec [this message]
2004-02-23 22:46 ` r3000 instruction set Kevin D. Kissell
2004-02-23 22:46   ` Kevin D. Kissell
  -- strict thread matches above, loose matches on Subject: below --
2004-03-01 15:38 Mark and Janice Juszczec
2004-02-23 16:56 Mark and Janice Juszczec
2004-02-23 17:07 ` Michael Uhler
2004-02-23 17:13 ` Maciej W. Rozycki
2004-02-23 17:21 ` Kevin D. Kissell
2004-02-23 17:21   ` Kevin D. Kissell
2004-02-23 17:59 ` Dominic Sweetman
2004-02-22  3:02 Mark and Janice Juszczec
2004-02-22  3:15 ` Michael Uhler
2004-02-22  9:32 ` Kevin D. Kissell
2004-02-22  9:32   ` Kevin D. Kissell
2004-02-22 12:31 ` Dominic Sweetman
2004-02-22 19:13 ` Eric Christopher
2004-02-22 21:52   ` Kevin D. Kissell
2004-02-22 21:52     ` Kevin D. Kissell
2004-02-23  3:03     ` Steven J. Hill
2004-02-23  7:03       ` Kevin D. Kissell
2004-02-23  7:03         ` Kevin D. Kissell
2004-02-23  3:37     ` Eric Christopher
2004-02-23  7:11       ` Kevin D. Kissell
2004-02-23  7:11         ` Kevin D. Kissell
2004-02-23  7:29         ` Eric Christopher

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=Law10-F10138dWMJ69i0000d0f4@hotmail.com \
    --to=juszczec@hotmail.com \
    --cc=dom@mips.com \
    --cc=echristo@redhat.com \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.org \
    --cc=uhler@mips.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