Graham Markall

Unfortunately I don't think there's a way to do that - a wrapper for `getZExtValue` would need to be added to the binding layer (in the `ffi` subdir then the...

@trbabb Many thanks for the PR and your efforts so far! I'm spending some time going through the llvmlite PR backlog, and I have a couple of questions on this...

#827 adds a lot more pass bindings - if we don't need to do much more than add the pass to llvmlite, then that PR could provide a reasonable template...

UTF-8 was originally used, but was switched to latin1 in https://github.com/numba/llvmlite/pull/53. If I switch the encoding to UTF-8, the test case that accompanied that PR doesn't fail (on Linux at...

Update: The test also passes on Windows.

I've opened https://github.com/numba/llvmlite/pull/655 with the change to see what happens on CI.

The CI tests seem to pass with utf-8, so I've pinged @sklam to ask for a further opinion.

The linked PR #655 is now ready for review.

There's no support for parsing existing bitcode at present. I'll label this as a feature request, though I note that it's a non-trivial amount of work to implement.

Indeed, objdump produces similar output to lief: ``` $ objdump -s test.elf test.elf: file format elf64-x86-64 Contents of section .text: 0000 48c1e220 4809c248 89d048c1 c03d4831 H.. H..H..H..=H1 0010 d048b901 20000480...