From: Joseph Myers <joseph@codesourcery.com>
To: <gcc@gcc.gnu.org>
Subject: C2x features status
Date: Thu, 20 Oct 2022 17:30:50 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2210201716000.71947@digraph.polyomino.org.uk> (raw)
I'm working on adding various C2x features to the C front end (and
elsewhere in GCC as applicable).
I suspect I won't get all the C2x features done for GCC 13. If anyone
else is interested in adding C2x features, I'd encourage looking at some
of the following, which I may well not get to for GCC 13 (and posting here
to avoid duplication of effort if working on such a feature):
* Bit-precise integer types (_BitInt) (see bug 102989) (integrated version
based on N2763, plus literal suffixes from N2775 and bit-fields from
N2969). Would require working with back-end maintainers and upstream ABI
groups, where available, to get ABIs defined for as many architectures as
possible, as well as some default ABI choice in GCC for architectures that
haven't defined the ABI for these types.
* [[unsequenced]] and [[reproducible]] attributes for function types. See
N2956. These are supposed to be similar to const and pure attributes, at
least in the absence of pointer and array function parameters (but note
they never affect type compatibility).
* Tag compatibility (N3037, alternative wording). Martin Uecker might
have patches for a draft version of this?
* Preprocessor #embed (N3017) (see bug 105863).
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2022-10-20 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 17:30 Joseph Myers [this message]
2022-10-21 18:31 ` Florian Weimer
2022-10-21 19:14 ` Marek Polacek
2022-10-21 19:29 ` Arsen Arsenović
2022-10-21 19:55 ` Florian Weimer
2022-10-21 20:26 ` Arsen Arsenović
2022-10-21 21:11 ` Joseph Myers
2022-10-21 22:13 ` Florian Weimer
2022-10-21 22:19 ` Joseph Myers
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 \
--in-reply-to=alpine.DEB.2.22.394.2210201716000.71947@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).