dyung wrote: > No, this specific code path has always produced incorrect output, even in > past versions of LLVM. I took care to keep the scope of the change as small > as possible to reduce the risk for this backport.
Given that it is not fixing a regression and not a fix with a broad impact, it is not really a candidate for inclusion on the release branch this late in the release cycle. The 22.x release branch will be created in about a month and the fix will be there. That being said, I will discuss with the other release managers to see what they think. https://github.com/llvm/llvm-project/pull/171522 _______________________________________________ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
