stuartarchibald

Does: ``` $ OPT="-O3" MTRIPLE="x86_64-unknown-unknown" MCPU="zenver1" opt -verify ${OPT} -mtriple=${MTRIPLE} -mcpu=${MCPU} fail.ll|llc ${OPT} -mtriple=${MTRIPLE} -mcpu=${MCPU} ``` help ?

Thanks for starting work on LLVM 14 support. In thinking about how to make it easier to review the changes needed, perhaps the following approach might work: * Creating a...

> Sure. I've created #831 for the code formatting changes. I'm going to leave this PR open so I can use it for the build farm. Thanks, keeping this open...

Closing as #837 implemented the feature based on this PR. Thanks all!

I agree with @gmarkall. Further, llvmlite's release cadence is pretty slow and the number of versions of a given release is proportional to the number of Python versions supported, so...

@seibert many thanks for doing the testing!

Thanks for the report. Do you have a reproducer ?

Think the IR generated is invalid. The `entry` block has no terminator. e.g. ```llvm define i32 @"mul7126777023838580747"(i32 %"a", i32 %"b") { entry: %".4" = alloca i32 store i32 %"a", i32*...

No problem. At the end of the `visit_Fun` you need to branch to the next block. `self.builder.branch(self.exit_block)` just before `self.end_function()` would do it, but isn't general as the next block...

Thanks for the report. Suspect this is related to https://github.com/numba/llvmlite/pull/502 and https://github.com/numba/llvmlite/pull/518. Are you building from the master branch? FWIW 0.30.0 wheels will be out within the next few days.