wrotki wrote: Turns out it was just an incorrect merge conflict resolution in our internal build (related to the changes timing wise), was fixed and now stuff works fine. Sorry for the false alarm, and thanks for looking @lenary. https://github.com/llvm/llvm-project/pull/136088