public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Jie Liu <lj8175@gmail.com>
Cc: java-patches@gcc.gnu.org, java@gcc.gnu.org,
	gcc-patches@gcc.gnu.org,
	       Joel Sherrill <joel.sherrill@oarcorp.com>
Subject: Re: [PATCH] [JAVA] patch for Java on RTEMS
Date: Mon, 15 Aug 2011 09:43:00 -0000	[thread overview]
Message-ID: <4E48EA37.6040300@redhat.com> (raw)
In-Reply-To: <CABc96T_MHjbKHrW8oHgBFW9k=79qeck_HehbxWA=CkWv4+k70Q@mail.gmail.com>

On 08/10/2011 06:00 PM, Jie Liu wrote:

> For the previous analysis "libjava patches for RTEMS"[1], there are 6
> cases need to pay more attention. PR18699, TLtest, Thread_Interrupt,
> Thread_Sleep_2, Throw_2 and bclink.
>
> After add patch to bdwgc for RTEMS pthread support[2]:
> PR18699                PASS after Modify       [A bug in boehm-gc on
> RTEMS, not related to libjava]
> TLtest                    PASS
> Thread_Interrupt      PASS
>
> For the other 3 cases:
> Thread_Sleep_2      PASS                       [After add patch to rtems]
> Throw_2                 PASS                       [After add patch to
> libjava, still need some work][3]
> bclink                    UnSupport
> [-findirect-dispatch do not support in this case]
>
> I think it's time to send out the patch for review, because it may
> need much time to modify. The patch is attached.

Looks OK, but there is no ChangeLog.  Do you have copyright
assignment?

Andrew.

  parent reply	other threads:[~2011-08-15  9:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 17:00 Jie Liu
2011-08-14 13:04 ` Jie Liu
2011-08-26 13:33   ` Ralf Corsepius
2011-08-15  9:43 ` Andrew Haley [this message]
2011-08-15 14:07   ` Jie Liu
2011-08-15 14:11     ` Andrew Haley
2011-08-26 13:20     ` Ralf Wildenhues

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=4E48EA37.6040300@redhat.com \
    --to=aph@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    --cc=joel.sherrill@oarcorp.com \
    --cc=lj8175@gmail.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).