News for hackers. Stuff that matters.

A comment on Jank development update – Moving to LLVM IR. Parent comment

Re:Jank development update – Moving to LLVM IR by fooker on Thursday October 17, 2024 @04:21AM (#41867511)
As long as you use the C++ API, the pace of change is reasonable.

If you try to keep by by generating textual IR, it can be a nightmare.

[ Parent | on HN ]
Re:Jank development update – Moving to LLVM IR by michielderhaeg on Thursday October 17, 2024 @05:43AM (#41867947)
I do agree that the pace is reasonable. Both with opaque pointers and the new pass manager API there was a quite a long transition period where both were supported before the old system was deprecated/removed. But with every new non-patch release, some part of the public API is changed and we have to adapt.
[ Parent | on HN ]
Re:Jank development update – Moving to LLVM IR by almostgotcaught on Thursday October 17, 2024 @07:13AM (#41868454)
> But with every new non-patch release, some part of the public API is changed and we have to adapt.

bumping only on major release is recipe for pain and misery. everyone project i'm familiar with bumps weekly against HEAD. much more manageable.

[ Parent | on HN ]
Re:Jank development update – Moving to LLVM IR by michielderhaeg on Thursday October 17, 2024 @05:40AM (#41867925)
I think the bitcode parsers (binary and textual) are quite backwards compatible. Old bitcode IR will be upgraded transparently. So you might not have to keep up.
[ Parent | on HN ]