[michielderhaeg]

Absolutely not. They do invasive changes all the time. At work we maintain an LLVM compatibility library that provides a stable interface across different LLVM versions. It has grown quite big over the years. The pure C interface is in comparison much more stable, but also quite limited.

Not just the API changes, the LLVM IR syntax can change drastically as well. E.g. not too long ago they switched from types pointer types to opaque pointers. `i32*` just becomes `ptr`. [1]

[1] https://llvm.org/docs/OpaquePointers.html

[fooker]

IR can be auto-upgraded between LLVM versions.

[almostgotcaught]

citation? i work on LLVM (like llvm/llvm-project) and i'm not aware of such a tool.

[theresistor]

The textual IR is not backwards compatible, but the bitcode format has been best-effort auto-upgradeable for as long as I've been involved (2006). The policy is documented here: https://llvm.org/docs/DeveloperPolicy.html#ir-backwards-comp...

[almostgotcaught]

bitcode policy i'm aware of - it's the "IR" part that caught my attention.

[mannycalavera42]

a pretty evident case of not almost got caught