h-vetinari wrote:

> All of this seems reasonable, are there any issues still blocking this from 
> landing?

I'm also in favour of this PR getting merged. FWIW, the reason I'm commenting a 
bunch here is not because I don't like the changes, but the exact opposite - 
I'd like to see them land for LLVM 20 (which means soon; branching for LLVM 18 
[was](https://discourse.llvm.org/t/llvm-18-release-schedule/76175) Jan 23rd, 
it's pretty safe to assume that LLVM 20 will branch mid-to-end of January).

https://github.com/llvm/llvm-project/pull/110217
_______________________________________________
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... Valentin Clement バレンタイン クレメン via llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... via llvm-branch-commits
  • [... via llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... via llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... via llvm-branch-commits
  • [... via llvm-branch-commits
  • [... via llvm-branch-commits
  • [... Joseph Huber via llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... Michael Kruse via llvm-branch-commits
  • [... via llvm-branch-commits
  • [... via llvm-branch-commits

Reply via email to