All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] llvm: update 3.5.2 to have a sane ARM JIT for OpenJDK-8
Date: Tue, 27 Oct 2015 15:09:15 -0700	[thread overview]
Message-ID: <562FF60B.405@balister.org> (raw)
In-Reply-To: <39E716D7-E36A-4696-9503-3DBB6B1C94DF@gmail.com>

On 10/27/2015 01:21 PM, Jens Rehsack wrote:
> 
>> Am 27.10.2015 um 21:15 schrieb Otavio Salvador <otavio.salvador@ossystems.com.br>:
>>
>> On Tue, Oct 27, 2015 at 6:04 PM, Jens Rehsack <rehsack@gmail.com> wrote:
>>>
>>> llvm introduced new JIT technology MCJIT with llvm 3.4 and fixes ARM in 3.5
>>> (see http://llvm.org/releases/3.5.2/docs/ReleaseNotes.html#changes-to-the-arm-backend).
>>>
>>> Ensure JIT is built with llvm
>>>
>>> Signed-off-by: Jens Rehsack <sno@netbsd.org>
>>
>> There is a patch to add LLVM 3.7[1]; I think this one can be dropped.
>>
>> 1. http://patchwork.openembedded.org/patch/106281/
> 
> I'v seen this and I guarantee that OpenJDK-8 will fail heavily with llvm3.7 - the guys
> put an end to an antiquated API's with each release, and OpenJDK's zeroshark uses lot's
> of them.

We'll need the 3.7 series llvm to support llvmpipe in newer mesa. The
mesa update will happen after the release and I want to be ready.

As Martin notes, we are setup to support multiple llvm versions and it
looks like we need to.

Philip

> 
> Cheers
> 


      parent reply	other threads:[~2015-10-27 22:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 20:04 [meta-oe][PATCH] llvm: update 3.5.2 to have a sane ARM JIT for OpenJDK-8 Jens Rehsack
2015-10-27 20:15 ` Otavio Salvador
2015-10-27 20:21   ` Jens Rehsack
2015-10-27 20:24     ` Otavio Salvador
2015-10-27 20:29       ` Jens Rehsack
2015-10-27 20:32       ` Martin Jansa
2015-10-27 21:19         ` Jens Rehsack
2015-10-27 22:09     ` Philip Balister [this message]

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=562FF60B.405@balister.org \
    --to=philip@balister.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 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.