ayzhao added a comment.

In D150122#4329401 <https://reviews.llvm.org/D150122#4329401>, @aaron.ballman 
wrote:

> I believe we are having another release of Clang 16, but @tstellar can 
> confirm or deny that.
>
> AIUI, there were a few issues holding us back from claiming complete support 
> (added @ayzhao as a reviewer in case he has a different opinion):
> https://github.com/llvm/llvm-project/issues/61145  (backported to 16.x)
> https://github.com/llvm/llvm-project/issues/62296  (backported to 16.x)
> https://github.com/llvm/llvm-project/issues/62266  (not backported)
> https://github.com/llvm/llvm-project/issues/61567  (not backported)
>
> If we backport the two other issues to 16, then I think the changes in this 
> review are fine. If we don't backport those two, I think we should claim 
> Clang 17 to be conservative.

I started the backporting process for the remaining 2 bugs. I'm doing 
https://github.com/llvm/llvm-project/issues/62266 first before doing 
https://github.com/llvm/llvm-project/issues/61567 because otherwise there will 
be a merge issue. Once those two commits are backported then this patch LGTM.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D150122/new/

https://reviews.llvm.org/D150122

_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to