[clang] [clang] check deduction consistency when partial ordering function templates (PR #100692)

2024-09-04 Thread Yashwant Singh via cfe-commits

yashssh wrote:

We at grace cpu are also facing same crashes on SPEC FP

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


[clang] [Clang][Parser] Accept P2741R3 (static_assert with user-generated message) in C++11 as an extension (PR #102044)

2024-09-16 Thread Yashwant Singh via cfe-commits

yashssh wrote:

Reigniting the discussion around `__cpp_static_assert`'s value set to `202306L` 
. We are seeing some failures in perennial c++20 tests who assume the value of 
macro to be `201411L` which is consistent with how GCC defines value of these 
macros (see https://godbolt.org/z/xE9bWsdKT)

>From the discussions earlier I'm getting the impression that this has more to 
>do with c++ standard not properly defining the values of these macros for 
>older revisions. What can be the best way forward to fix this? Have it 
>consistent with GCC?


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


[clang] [Clang][Parser] Accept P2741R3 (static_assert with user-generated message) in C++11 as an extension (PR #102044)

2024-09-16 Thread Yashwant Singh via cfe-commits

yashssh wrote:

https://isocpp.org/files/papers/N4860.pdf according to this, cpp_static_assert 
should be 201411L for c++20


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