[nicl] branch is now closed

Samuel Audet samuel.audet at gmail.com
Sun Sep 9 11:59:07 UTC 2018

On 09/03/2018 11:55 AM, Henry Jen wrote:
>> However, the fact is, there is still no cooperation whatsoever between Panama and GraalVM, but the parallel are striking, see this for example:https://cornerwings.github.io/2018/07/graal-native-methods/
>> 	Method		 	Time per iteration
>> 	graal/native-image 	76.11 ns
>> 	jni/unsafe 		109.42 ns
>> Trying to get these teams on the same page might be a good start here. Why isn't this happening? I think it would be a useful exercise to understand the internal politics of Oracle, but maybe we don't need to know the details, just that the internal disputes are taken care of…
> Correct me if I am wrong, but those are different approaches and not exclusive. We noted that Graal polyglot solution, but it needs source code or LLVM bitcode, while here at Panama is focused on platform native format.

Sulong uses LLVM to support native languages like Fortran and C++, as 
well as their native libraries.

The module to call system functions isn't part of Sulong, it's part of 
the "Substrate VM", which is unrelated to LLVM or Sulong.

That said, unlike Panama, the GraalVM team isn't against relying on 
other libraries such as LLVM to support things like C++... I'll repeat 
as many times as I keep hearing people mentioning C++ alongside Panama: 
You will need to figure out how to cooperate with the community!


More information about the panama-dev mailing list