You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux x64, Linux arm64, Linux arm32, macOS x64, macOS arm64, Windows x64, Windows x86, Windows arm64
JDK
Zulu OpenJDK 21
Module
LLVM
Bug description
There is a code generation bug involving the LLVMGetBufferStart function, as it falsely returns a String instead of a long, because the code generator seems to assume String based on the native function's const char* return type. Imo LLVM itself should just return a (const) void* there.. But that's not to question for me xD
This small issue has been bugging me for a while as i have to use the nGetBufferStart function instead as a workaround.
Thanks for the great work on the LLVM bindings otherwise, really nice to quickly build a compiler in Java :)
Stacktrace or crash log output
No response
The text was updated successfully, but these errors were encountered:
Version
3.3.3
Platform
Linux x64, Linux arm64, Linux arm32, macOS x64, macOS arm64, Windows x64, Windows x86, Windows arm64
JDK
Zulu OpenJDK 21
Module
LLVM
Bug description
There is a code generation bug involving the LLVMGetBufferStart function, as it falsely returns a
String
instead of along
, because the code generator seems to assume String based on the native function'sconst char*
return type. Imo LLVM itself should just return a (const)void*
there.. But that's not to question for me xDThis small issue has been bugging me for a while as i have to use the
nGetBufferStart
function instead as a workaround.Thanks for the great work on the LLVM bindings otherwise, really nice to quickly build a compiler in Java :)
Stacktrace or crash log output
No response
The text was updated successfully, but these errors were encountered: