See "[PATCH v2] c++: Add support for -std=c++2b" for fixes.
On Fri, Jan 8, 2021 at 3:16 PM Marek Polacek wrote:
>
> I think we should consider making this -std=c++23 right away this time,
> since we're on a three-year release schedule. Up to Jason though.
>
> Marek
>
I think we should consider making this -std=c++23 right away this time,
since we're on a three-year release schedule. Up to Jason though.
Marek
On Fri, Jan 08, 2021 at 12:48:51AM +, Paul Fee via Gcc-patches wrote:
> Derived from the changes that added C++2a support in 2017.
> https://gcc.gnu.org/g:026a79f70cf33f836ea5275eda72d4870a3041e5
>
> No C++2b features are added here.
> Use of -std=c++2b sets __cplusplus to 202101L.
What Jon w
On Fri, 8 Jan 2021, 00:50 Paul Fee via Libstdc++,
wrote:
> Derived from the changes that added C++2a support in 2017.
> https://gcc.gnu.org/g:026a79f70cf33f836ea5275eda72d4870a3041e5
>
> No C++2b features are added here.
> Use of -std=c++2b sets __cplusplus to 202101L.
>
I wonder if 202100L woul
Derived from the changes that added C++2a support in 2017.
https://gcc.gnu.org/g:026a79f70cf33f836ea5275eda72d4870a3041e5
No C++2b features are added here.
Use of -std=c++2b sets __cplusplus to 202101L.
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 5541e694bb3..3a0d452b62b 100644
--- a/gcc/Ch
