On 1/31/24 08:55, Richard Biener wrote:
On Wed, Jan 31, 2024 at 2:53 PM Jason Merrill <ja...@redhat.com> wrote:
On 1/31/24 03:40, Richard Biener wrote:
On Wed, Jan 31, 2024 at 12:19 AM Marek Polacek <pola...@redhat.com> wrote:
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
We plan to deprecate -fconcepts-ts in GCC 15 and remove the flag_concepts_ts
code. This note is an admonishing reminder to convert the Concepts TS
code to C++20 Concepts.
What does "deprecated in GCC 15" mean? Given you output the notice with
GCC 14 it would be better to state when it's going to be removed -
it's effectively
"deprecated" right now then? Or will it continue to "work" forever
until it bitrots?
Agreed, it's deprecated now. We talked about it having no effect in GCC
15; the message could say that. Or we could leave it vague and just say
it's deprecated.
Please also update invoke.texi.
Btw, should -std=c++20 -fconcepts-ts be rejected?
No, that makes sense, it means C++20 plus the TS extensions that didn't
make it into the standard.
I suppose -std=c++20 enables -fconcepts by default, it also seems to accept
-std=c++20
-fno-concepts ...
I don't know why anyone would do that, but I don't see a reason to
prohibit it either.
Jason
