dyung wrote: Hi, at this point in the 21.x release branch we are only accepting patches that fix regressions or major issues. Was the problem being fixed here a recent regression? From a quick look at the history, the code being replaced was introduced around the LLVM 18 time frame, so it has been around for a while.
What are the implications if we do not accept this change into the 21.x release branch? Would something be broken that cannot be worked around or otherwise fixed without it? At this point, I am leaning towards not including the fix and waiting for LLVM 22 for it, but if you feel strongly that it should be included, please let us know why and I can consult with the other release managers to see how they feel on the issue. https://github.com/llvm/llvm-project/pull/168371 _______________________________________________ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
