From: "Xerxes Rånby" <xerxes@zafena.se>
To: openembedded-devel@lists.openembedded.org, jalimo-info@lists.evolvis.org
Subject: OpenJDK-6 ARM Shark LLVM JIT testing
Date: Wed, 14 Jul 2010 19:37:03 +0200 [thread overview]
Message-ID: <4C3DF5BF.9040103@zafena.se> (raw)
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=1ea15a2cd73178c3fbab36b544a6601b1d1c32bf
This patch will make OpenJDK use the best ARM CPU features available
when generating code using the Shark JIT.
To test shark build the openjdk-6 package and run your favorite java
application with the -shark switch.
java -shark foo
The Shark JIT uses LLVM for its in memory code generation and the
stability of Shark depends on
how much the LLVM JIT have been tested on various ARM CPUs.
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.
If LLVM asserts then you can help generate LLVM testcases by running
shark with this switch:
java -shark
-XX:SharkPrintBitcodeOf=insert::problematic:method::name::here foo
And attach the output in the report.
I have written a small guide on how to get Shark LLVM JIT CodeGen crash
bugs fixed:
http://labb.zafena.se/?p=362
Cheers and have a great day!
Xerxes
next reply other threads:[~2010-07-14 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 17:37 Xerxes Rånby [this message]
2010-07-14 19:47 ` OpenJDK-6 ARM Shark LLVM JIT testing Henning Heinold
2010-07-14 20:43 ` Marcin Juszkiewicz
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=4C3DF5BF.9040103@zafena.se \
--to=xerxes@zafena.se \
--cc=jalimo-info@lists.evolvis.org \
--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