public inbox for
 help / color / mirror / Atom feed
From: Jie Liu <>
To: RTEMS Mailing List <>,
Cc: Joel Sherrill <>
Subject: GCJ Porting for RTEMS Status Report
Date: Sun, 12 Jun 2011 17:15:00 -0000	[thread overview]
Message-ID: <> (raw)


First, let us look at an HelloWorld example with exception and thread,
the is:
public class HelloWorld{
   public static void main(String args[]){
      ThreadTest t=new ThreadTest();
      Thread t1=new Thread(t);
      System.out.println("GCJ For RTEMS in Java!---in");
        System.out.println(args[100]+"for raise an exception");
      }catch(Exception e){
        System.out.println(e.getMessage()+"---in an Exception");
class ThreadTest extends Thread{
  public void run(){
    System.out.println("ThreadTest from HelloWorld!---in a new thread");

Compiling it using cross gcj and linking with rtems system, we get a
HelloWorld.exe. And then, run it on qemu as:
qemu -m 512 -boot a -cpu 486 -fda /home/rtems/qemu/pc386_fda -hda
fat:/home/rtems/qemu/hd -monitor null -nographic -serial stdio

The output is:
Initialized console on port COM1 9600-8-N-1
GCJ For RTEMS in Java!---in
100---in an Exception
ThreadTest from HelloWorld!---in a new thread
EXECUTIVE SHUTDOWN! Any key to reboot...

Is this interesting?

In the last few months, I have
--Porting bdwgc to RTEMS/I386
--Use RTEMS’s pthread for GCJ Porting
--Fix many many problems in compiling, linking and running
--Have a cross gdb environment for source code level debug
and next step I will
-- Start focusing on running the testsuite and fix encountered problem
-- Move to other architectures and repeat this progress
--Submitting patches to related community

If you are interested in, welcome! Do not hesitate to contact me. :)

Best Regards,

             reply	other threads:[~2011-06-12 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-12 17:15 Jie Liu [this message]
2011-06-13  9:14 ` Andrew Haley
2011-06-13 22:12   ` Franklin Chou

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).