All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-devel@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-java][PATCH] OpenJDK-8: For x86 and ARM
Date: Fri, 11 Sep 2015 08:55:43 +0100	[thread overview]
Message-ID: <1441958143.24871.377.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKrt7jhFtN6JWFqqbSnJxyX4kAc77CkigOCChkV4gz=-Cw@mail.gmail.com>

On Fri, 2015-08-28 at 14:29 -0300, Otavio Salvador wrote:
> On Fri, Aug 28, 2015 at 4:12 AM, Richard Leitner
> <richard.leitner@skidata.com> wrote:
> > On 08/28/2015 03:14 AM, Vinay K. Awasthi wrote:
> >> Rebased it again with latest change-set and tested it on oe-core master with latest mate-openembedded.
> >>
> >> There is no change in recipe.
> >>
> >> This enables OpenJDK-8 jre/jdk for x86 and ARM.
> >>
> >> This recipe is tested for arm (zero VM) and x86 (hotspot vm).
> >>
> >> To build just use bitbake openjdk-8.
> >
> > I successfully compiled and tested it for/on an ARMv7 Cortex A9 CPU:
> > # /usr/lib/jvm/java-8-openjdk/jre/bin/java -version
> > openjdk version "1.8.0-internal"
> > OpenJDK Runtime Environment (build 1.8.0-internal-leri_2015_08_28_08_47-b00)
> > OpenJDK Zero VM (build 25.60-b23, interpreted mode)
> >
> > Also X11/awt/swing works fine! Only problem for me is that ZeroVM is
> > running in "interpreted mode". Therefore my programs are running really
> > slow.
> >
> > Was the "mixed mode" available/working in your tests?
> >
> > IMHO a working JIT (=> mixed-mode) is a must-have for merging this patch
> > upstream. What do you think Otavio?
> 
> Yes, I agree. There are other people working in OpenJDK 8 here[1] (at
> ml) it seems so maybe we could share some ideas on how to fix it.

I'm hearing there is a little frustration about moving forward with
this. I'd like to suggest that a staged approach might be better in this
case, for example if OpenJDK-8 is working on IA, how about adding it
with:

# mixed-mode isn't working on ARM yet
COMPATIBLE_HOST = '(i.86|x86_64).*-linux'

With a large change like this, I think its perhaps ok to take a staged
approach, as long as its clear what is/isn't expected to work?
If/as/when the ARM people have time to make it work there, patches can
be sent to change that? This way it unblocks people and doesn't hold
keen contributors back.

Cheers,

Richard




  reply	other threads:[~2015-09-11  7:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28  1:14 [meta-java][PATCH] OpenJDK-8: For x86 and ARM Vinay K. Awasthi
2015-08-28  7:12 ` Richard Leitner
2015-08-28 12:37   ` Awasthi, Vinay K
2015-08-28 17:29   ` Otavio Salvador
2015-09-11  7:55     ` Richard Purdie [this message]
2015-09-11 12:11       ` Otavio Salvador
  -- strict thread matches above, loose matches on Subject: below --
2015-08-20  0:55 Vinay K. Awasthi
2015-09-30 21:15 ` Awasthi, Vinay K
2015-09-30 21:20   ` Otavio Salvador
2015-09-30 21:30     ` Awasthi, Vinay K
2015-09-30 22:58     ` Awasthi, Vinay K
2015-10-02 13:27       ` Otavio Salvador
2015-10-02 15:50       ` Jens Rehsack
2015-10-02 16:42         ` Otavio Salvador
2015-10-02 17:15           ` Jens Rehsack
2015-10-02 16:44         ` Awasthi, Vinay K

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=1441958143.24871.377.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.