> Am 27.10.2015 um 21:32 schrieb Martin Jansa <[email protected]>:
> 
> On Tue, Oct 27, 2015 at 06:24:52PM -0200, Otavio Salvador wrote:
>> On Tue, Oct 27, 2015 at 6:21 PM, Jens Rehsack <[email protected]> wrote:
>>> 
>>>> Am 27.10.2015 um 21:15 schrieb Otavio Salvador 
>>>> <[email protected]>:
>>>> 
>>>> On Tue, Oct 27, 2015 at 6:04 PM, Jens Rehsack <[email protected]> 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 <[email protected]>
>>>> 
>>>> 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.
>> 
>> So we will need to figure how to deal with this. I see following options:
>> 
>> - add needed llvm recipe in meta-java (I dislike this)
>> - fix openjdk
>> - update openjdk so it work with 3.7 (preferred)
> 
> I don't mind having all 3 llvm versions in parallel until all this is
> sorted out.
> 
> People can select the right one based on mesa version they are using and
> 3.8 for OpenJDK.
> 
> But I would appreciate this recipe rebased on top of Philip's (or vice
> versa), because I don't have spare time to text it with newer mesa
> Philip is using or with OpenJDK Jens is using.

Since OpenJDK waits for autoconf patch anyway, I'm happy to rebase my
patch when Philip's is in.

I'm also happy to try out how complex a move to 3.7 will be for openjdk-8 if
I find a tuit. I think, next week or so we'll make an initial decision
about our way to get a JVM with JIT support.

Cheers
-- 
Jens Rehsack - [email protected]

-- 
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Reply via email to