Re: [Jikesrvm-researchers] build on ppc405

[Paul H. <ph...@st...>]

I've successfully run JikesRVM on Montavista linux on the Xilinx embedded
PowerPC405 on the ml310 board.  It seems that the archive search function
doesn't work for me but some of the posts are here:
http://sourceforge.net/mailarchive/forum.php?forum_id=3D43937&max_rows=3D=
25&offset=3D25&style=3Dultimate&viewmonth=3D200406

The followup post on how I got this all works seems to not be there (whic=
h
is a shame) so I'll have to hunt for that.  It's also a shame that google
doesn't have these in their archive.  GCC comes with the Montavista Linux
port to the Xilinx FPGAs.  I don't think it makes sense to run jikesrvm
bare without the Linux intermediate layer.

Bottom line--I used a precompiled powerpc classpath gratiously provided b=
y
someone on this list.  The main issue is that the Xilinx embedded
PowerPC405 does not have a floating point unit.  The linux kernel soft
float traps any FPU opcodes and emulates them.  However, the gcc compiled
parts of the jikesrvm used the gcc emulation without emiting FPU opcodes.=
=20
Thus in effect there were two versions of the FP register file.  I needed
to add patch up code to the code generator to transfer virtual FPU
registers to/from the kernel soft emulation and the gcc emulation.  Not t=
he
most elegant (or performance efficient) but it worked.

All the rest was a normal build.  Have you already compiled jikesrvm  nat=
ive
on x86/etc so you have the flow down?   I started there to get my bearing=
s
since the whole jikesrvm package is reasonably complex.

Paul

Quoting =A4B =B4=D3=A8| <fro...@ho...>:
> Dear all,
> after the step jbuild on the host machine
> it asks us to do the step jbuild -booter on the target machine
> for me , it is Xilinx powerpc 405/ML310
> but there are some messages make me confused
> at line 13
> It checks the tool gcc
> but as I know , there is no C compiler on powerpc 405
> how could I solve this problem?
> thanks a lot
> ---------------
> 01 %./jbuild -booter
> 02 Configuring for powerpc-unknown-linux-gnu
> 03 checking build system type... powerpc-unknown-linux-gnu
> 04 checking host system type... powerpc-unknown-linux-gnu
> 05 checking target system type... powerpc-unknown-linux-gnu
> 06 checking for a BSD-compatible install... /usr/bin/install -c
> 07 checking whether build environment is sane... yes
> 08 checking for gawk... /bin/awk
> 09 checking whether make sets $(MAKE)... yes
> 10 checking whether ln -s works... no, using cp -p
> 11 checking for a BSD-compatible install... /usr/bin/install -c
> 12 checking for style of include used by make... GNU
> 13 checking for gcc... /dev/usb/rvmRoot/rvm/bin/gcc -w -g -O -Wa,-mppc
> 14 checking for C compiler default output file name... configure: error=
:
> C
> compiler cannot create executables
> 15 See `config.log' for more details.
> 16 jBuildClasspathJar: Aborted due to a command exiting with error stat=
us
> (77)
> 17 jbuild:164: some command we just ran (probably with a final argument
> of
> "--check") exited with status 77,
> 18 jbuild: Aborting execution.
> 19 jbuild: Exiting unexpectedly with status 77.
> 20 jbuild: Cleaning up...
> 21 jbuild: ...no cleanup was needed.
> ---------------------------------
>
> _________________________________________________________________
> MSN Messenger 7.0 =B7m=C2A=AA=A9=BC=F6=AFP=A4U=B8=FC=A4=A4=A1G=A7O=BF=F9=
=B9L=B6W=BB=C5=AA=BA=B0=CA=B5e=A7=D6=BB=BC
> http://messenger.msn.com.tw/beta
>
>