A patch has been posted to add SH4 support to nanojit. We should quickly add the compilation of this shell to the tamarin build system to make sure that it continues to compile as additional changes come in to nanojit. Need to know which compiler is being supported so we can add it to our build machines as necessary.

I'm using the compilers from the STLinux distro (both native and cross): ftp://ftp.stlinux.com/pub/stlinux/2.4/STLinux/sh4/ Technically I would like to support any recent GCC/SH4 compiler, so feel free to pick yours from anywhere.

Using sh4 compilers from this location, cross compiling on ubuntu x86: http://impactlinux.com/fwl/downloads/binaries/cross-compiler-sh4.tar.bz2 Version information: Invoked as /home/build/tools/cross-compiler-sh4/bin/sh4-g++ Reference path: /home/build/tools/cross-compiler-sh4/bin/.. arg[ 0] = raw++ arg[ 1] = -fno-use-cxa-atexit arg[ 2] = -U__nptl__ arg[ 3] = -v Using built-in specs. Target: sh-superh-linux Configured with: /home/landley/temp/firmware/build/temp-sh4/gcc-core/configure --target=sh-superh-linux --prefix=/home/landley/temp/firmware/build/cross-compiler-sh4 --disable-multilib --disable-nls --enable-c99 --enable-long-long --enable-__cxa_atexit --enable-languages=c,c++ --disable-libstdcxx-pch --program-prefix=sh4- --enable-threads=posix --enable-shared --build=x86_64-walrus-linux --host=sh-superh-linux --enable-sjlj-exceptions Thread model: posix gcc version 4.2.1

Setting up asteamlin8 with Fedora Core 13 and STLinux toolchain. I was unable to get the toolchain working under ubuntu properly, but have had no problems on the officially supported platforms of RedHat Ent. and Fedora Here are the steps I have done to get the toolchain working: 1) Setup urlgrabber python packge: http://pypi.python.org/packages/source/u/urlgrabber/urlgrabber-3.1.0.tar.gz#md5=18dd62b234da85fd76acd6ba29460743 2) Get and mount STLinux 2.4 iso: wget ftp://ftp.stlinux.com/pub/stlinux/2.4/iso/STLinux-2.4-sh4-20100401.iso mkdir /mnt/cdrom mount -o loop,ro -t iso9660 -r STLinux-2.4-sh4-20100401.iso /mnt/cdrom /mnt/cdrom ./install all-sh4-glibc Toolchain can then be used in /opt/STM/STLinux-2.4/devkit/sh4/bin

linux-sh4 buildslave runs on the SH4 box and runs smokes and acceptance passes linux2 buildslave currently only builds the SH4 binaries and nothing else

Acceptance run times: release hybrid -> 14:06 release interp -> 16:09 release JIT -> 37:51 debug hybrid -> 1:58:32

Comment on attachment 471110 [details] [diff] [review] add linux-sh4 and linux2 build slaves Looks good. Can you add a comment to explain why the following steps are commented out: + #sb_linux2_compile_factory.addStep(compile_buildcheck_local) + #sb_linux2_compile_factory.addStep(util_upload_asteam_local) + #linux2_compile_factory.addStep(compile_buildcheck_local) + #linux2_compile_factory.addStep(util_upload_asteam_local)

Comment on attachment 471110 [details] [diff] [review] add linux-sh4 and linux2 build slaves Patch pushed as 5258:c3a164934c39

changeset: 5692:f22f6ccdc462 user: Brent Baker <brbaker@adobe.com> summary: Bug 568493: when the SH4 build steps were added the debug step was improperly named. (r+cpeyer) buildbot: send email notifications of failures in the deep and performance phase of the build to the QE team (r+cpeyer) http://hg.mozilla.org/tamarin-redux/rev/f22f6ccdc462