JEP draft: Remove Shark compiler

Roman Kennke rkennke at redhat.com
Wed Oct 11 15:39:30 UTC 2017


Am 11.10.2017 um 17:33 schrieb Andrew Hughes:
> On 11 October 2017 at 15:27, Roman Kennke <rkennke at redhat.com> wrote:
>> I have drafted a JEP with the intention to remove the Shark compiler:
>>
>> https://bugs.openjdk.java.net/browse/JDK-8189173
>>
>> I would like to get some opinions here before I submit this JEP for real. In
>> particular:
>>
>> - If anybody has a need for Shark
>> - If anybody wants to step up to maintain it
>>
>> speak up now!
>>
>> Further, if you have anything that is missing or needs to be changed in the
>> JEP draft, please let me know.
>>
>> Thanks,
>>
>> Roman
>>
> Yeah, I agree it's been superseded for the use cases it was originally
> created for.
> Personally, I've never been able to get the right combination of Shark and LLVM
> to even build it.
>
> On the Zero note, I'm in favour of keeping that alive, even if we reach a point
> where we don't need to ship VMs that use it. It comes in useful when porting
> to new architectures and also as a fallback where bugs are encountered
> with JIT ports.

Hi Andrew,

I agree about Zero. I have put this under 'non-goals':

"It is not a goal of this JEP to remove the Zero interpreter (which is 
the basis for Shark)."

Roman



More information about the zero-dev mailing list