Tanner Gooding
Tanner Gooding
> I mean LLVM makes a lot of breaking changes (or at least did in the past). Couldn't we follow the same model? I'm not worried about introducing breaks between...
> Could we not, in principle, walk the declarations of the LLVM C++ API using ClangSharp and generate managed wrappers? Not easily. There isn't a 1-to-1 mapping (or even always...
> I haven't had as much time to invest into LLVMSharp which is why its managed wrapper isn't as far done as the ClangSharp version is. That being said, now...
I've split the project into `LLVMSharp` and `LLVMSharp.Interop`. The `LLVMSharp.Interop` bindings should be generally "stable" each release and so I'll likely be publishing 12.0.0 as "stable" tomorrow. `LLVMSharp` is the...
Yes. Happy to take a PR if someone would like to fix this :)
This would be a larger undertaking as LLD does not have C bindings provided out of the box. I'd be happy to consider providing such bindings *if* official C bindings...
There was some discussion on the actual PR: https://github.com/microsoft/LLVMSharp/pull/105 The low level bindings made generating and picking up updates much easier (and ensured the lowest level API was correct). However,...
I've started the work on a replacement for `LLVMSharp.API` here: https://github.com/microsoft/LLVMSharp/pull/137
Could you clarify which version of LLVMSharp you're using? For reference, this is incorrect usage and likely and I'm actually surprised its producing IR at all: * `LLVMConstReal` just calls...
Thanks! That all lines up then. I'm unsure why its not erroring, as it really should be. I'll leave this issue open to track adding some diagnostics on the LLVMSharp...