On Thu, Feb 5, 2026 at 9:02 PM Nathan Chancellor <[email protected]> wrote: > > Thanks for the CC, I had not seen that issue. LLVM 22 is currently in > the -rc phase and I see that the fix has been merged into the > release/22.x branch as of yesterday so it should be in LLVM 21.1.0-rc3 > when it get released on February 10. LLVM 21.1.8 was the last release of > the 21.x series (hard to keep up with all the numbers...) and it sounds > like this is only a regression from the LLVM 22 development cycle.
Yeah, sorry, mixed up 21.1.9 with the potential 22.1.9 in summer this year, bah! Fixed my comment in the issue to avoid confusion. Thanks! Cheers, Miguel
