From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OpenJDK-6 ARM Shark LLVM JIT testing
Date: Wed, 14 Jul 2010 22:43:34 +0200 [thread overview]
Message-ID: <201007142243.36837.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <4C3DF5BF.9040103@zafena.se>
Dnia środa, 14 lipca 2010 o 19:37:03 Xerxes Rånby napisał(a):
> Hi all!
>
> I have committed some ARM Shark CPU features auto-detection code into
> oe.dev.
> http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=1ea15a2cd7317
> 8c3fbab36b544a6601b1d1c32bf This patch will make OpenJDK use the best ARM
> CPU features available when generating code using the Shark JIT.
> I need your help in order to find and catch the LLVM JIT bugs by testing
> running Shark and report if
> LLVM asserts during code generation.
LLVM does not supports Thumb - thats hurt. Ubuntu had to disable Shark to get
openjdk-6 built for armel.
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
next prev parent reply other threads:[~2010-07-14 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 17:37 OpenJDK-6 ARM Shark LLVM JIT testing Xerxes Rånby
2010-07-14 19:47 ` Henning Heinold
2010-07-14 20:43 ` Marcin Juszkiewicz [this message]
2010-07-15 13:44 ` Xerxes Rånby
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=201007142243.36837.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--cc=openembedded-devel@lists.openembedded.org \
/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