search for: llvmified

...nd as a distro, we have to make sure they all work (so they agree on the same API), preferably without having to ship multiple versions of LLVM and preferably without having to patch external code too much to adjust to API changes. In OpenMandriva, we have to keep Mesa, creduce, emscripten and the LLVMified Qt moc working (list expected to grow -- ultimately we'd also like to use the system LLVM libraries for the swift compiler). In AOSP, RenderScript relies on the LLVM API, but there's nothing else using it, so there's currently no need to force a common version of the API between differe...

...ke sure they all work (so they > agree on the same API), preferably without having to ship multiple versions > of LLVM and preferably without having to patch external code too much to > adjust to API changes. > > In OpenMandriva, we have to keep Mesa, creduce, emscripten and the > LLVMified Qt moc working (list expected to grow -- ultimately we'd also > like to use the system LLVM libraries for the swift compiler). > In AOSP, RenderScript relies on the LLVM API, but there's nothing else > using it, so there's currently no need to force a common version of the API...

FWIW, for our ARM Compiler product, we follow top-of-trunk, not the releases. Next to picking up new functionality quicker, it also allows us to detect regressions in LLVM against our in-house testing quickly, not 6 months later. We find that when we find a regression within 24 to 48 hours of the commit introducing it, it's much cheaper to get it fixed. In my opinion, it would be better