GCC 16 considering changing default to C++20

From: Marek Polacek To: GCC , Jonathan Wakely , Jason Merrill Subject: Change the default C++ dialect to gnu++20 Date: Mon, 3 Nov 2025 13:34:28 -0500 [thread overview] Message-ID: (raw) I would like us to declare that C++20 is no longer experimental and change the default dialect to gnu++20. Last time we changed the default was over 5 years ago in GCC 11: and before that in 2015 in GCC 6.1, so this happens roughly every 5 years. I had been hoping to move to C++20 in GCC 15 (see bug 113920), but at that time libstdc++ still had incomplete C++20 support and the compiler had issues to iron out (mangling of concepts, modules work, etc.). Are we ready now? Is anyone aware of any blockers? Presumably we still wouldn't enable Modules by default. I'm willing to do the work if we decide that it's time to switch the default C++ dialect (that includes updating cxx-status.html and adding a new caveat to changes.html). Marek

Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ [email protected] \ [email protected] \ [email protected] \ [email protected] \ [email protected] \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).