vbvictor wrote:

> That's probably happening due to incomplete C++20 support in either Clang 14 
> or the GNU libstdc++ 12.

Current standard that LLVM use is c++17. But we generally should support 
compilers at [least 3 years of 
compilers](https://llvm.org/docs/DeveloperPolicy.html#updating-toolchain-requirements).

> Would it be possible to cherry-pick the fix to the release/20.x branch?

I don't have much knowledge on cherry-picking to release, but the latest 
release of 20.x could be on Jul 8th (if it even happens, see 
https://llvm.org/). I have a slight feeling that it may not worth 
cherry-picking, If LLVM is compiled from source, would it be feasible to just 
use 21st LLVM branch that will be released soon, 
[gjasny](https://github.com/gjasny)?




https://github.com/llvm/llvm-project/pull/147048
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to