philnik777 wrote:

Oh shit. I just realized that this is most likely a latent bug no matter what. 
We build the module with Clang 18, and then essentially try to load it with 
Clang 17 (aka Clang Tidy 17). AFAIK that's not guaranteed to work, and probably 
just happens to work currently with Clang 17 building and Clang 18 loading the 
module (assuming we even test that right now?). I think we may have to always 
match the Clang and Clang Tidy versions we use.

https://github.com/llvm/llvm-project/pull/76268
_______________________________________________
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

Reply via email to