From: Ken Matsui <kmatsui@gcc.gnu.org>
To: gcc-patches@gcc.gnu.org
Cc: jason@redhat.com, ppalka@redhat.com, Ken Matsui <kmatsui@gcc.gnu.org>
Subject: [PATCH v2 08/12] extend.texi: Add documentation for __is_object
Date: Thu, 14 Mar 2024 00:22:31 -0700 [thread overview]
Message-ID: <20240314072234.880769-9-kmatsui@gcc.gnu.org> (raw)
In-Reply-To: <20240302002229.308001-1-kmatsui@gcc.gnu.org>
gcc/ChangeLog:
* doc/extend.texi (__is_object): New documentation.
Signed-off-by: Ken Matsui <kmatsui@gcc.gnu.org>
---
gcc/doc/extend.texi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 86ac0c7ed07..293eb5706f9 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -29665,6 +29665,11 @@ If @var{type} is a pointer to member type ([dcl.mptr]) the trait is
@code{true}, else it is @code{false}.
@enddefbuiltin
+@defbuiltin{bool __is_object (@var{type})}
+If @var{type} is an object type ([basic.types]) the trait is
+@code{true}, else it is @code{false}.
+@enddefbuiltin
+
@defbuiltin{bool __is_pod (@var{type})}
If @var{type} is a cv POD type ([basic.types]) then the trait is @code{true},
else it is @code{false}.
--
2.44.0
next prev parent reply other threads:[~2024-03-14 7:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 0:22 [PATCH 01/11] gcc/doc/extend.texi: Sort built-in traits alphabetically Ken Matsui
2024-03-02 0:22 ` [PATCH 02/11] gcc/doc/extend.texi: Add documentation for __is_array Ken Matsui
2024-03-02 0:22 ` [PATCH 03/11] gcc/doc/extend.texi: Add documentation for __is_bounded_array Ken Matsui
2024-03-02 0:22 ` [PATCH 04/11] gcc/doc/extend.texi: Add documentation for __is_function Ken Matsui
2024-03-02 0:22 ` [PATCH 05/11] gcc/doc/extend.texi: Add documentation for __is_member_function_pointer Ken Matsui
2024-03-02 0:22 ` [PATCH 06/11] gcc/doc/extend.texi: Add documentation for __is_member_object_pointer Ken Matsui
2024-03-02 0:22 ` [PATCH 07/11] gcc/doc/extend.texi: Add documentation for __is_member_pointer Ken Matsui
2024-03-02 0:22 ` [PATCH 08/11] gcc/doc/extend.texi: Add documentation for __is_object Ken Matsui
2024-03-02 0:22 ` [PATCH 09/11] gcc/doc/extend.texi: Add documentation for __is_reference Ken Matsui
2024-03-02 0:22 ` [PATCH 10/11] gcc/doc/extend.texi: Add documentation for __is_scoped_enum Ken Matsui
2024-03-02 0:22 ` [PATCH 11/11] gcc/doc/extend.texi: Add documentation for __remove_pointer Ken Matsui
2024-03-02 16:00 ` [PATCH 01/11] gcc/doc/extend.texi: Sort built-in traits alphabetically Ken Matsui
2024-03-08 16:38 ` Patrick Palka
2024-03-08 17:46 ` Ken Matsui
2024-03-14 7:22 ` [PATCH v2 01/12] extend.texi: Arrange pre-existing " Ken Matsui
2024-03-14 7:38 ` Ken Matsui
2024-03-15 7:20 ` [PATCH v3 1/2] " Ken Matsui
2024-03-15 7:20 ` [PATCH v3 2/2] extend.texi: Add documentation for all missing built-in traits [PR87343] Ken Matsui
2024-03-16 9:47 ` [PATCH v4 " Ken Matsui
2024-03-14 7:22 ` [PATCH v2 02/12] extend.texi: Add documentation for __is_array Ken Matsui
2024-03-14 7:22 ` [PATCH v2 03/12] extend.texi: Add documentation for __is_bounded_array Ken Matsui
2024-03-14 7:22 ` [PATCH v2 04/12] extend.texi: Add documentation for __is_function Ken Matsui
2024-03-14 7:22 ` [PATCH v2 05/12] extend.texi: Add documentation for __is_member_function_pointer Ken Matsui
2024-03-14 7:22 ` [PATCH v2 06/12] extend.texi: Add documentation for __is_member_object_pointer Ken Matsui
2024-03-14 7:22 ` [PATCH v2 07/12] extend.texi: Add documentation for __is_member_pointer Ken Matsui
2024-03-14 7:22 ` Ken Matsui [this message]
2024-03-14 7:22 ` [PATCH v2 09/12] extend.texi: Add documentation for __is_reference Ken Matsui
2024-03-14 7:22 ` [PATCH v2 10/12] extend.texi: Add documentation for __is_scoped_enum Ken Matsui
2024-03-14 7:22 ` [PATCH v2 11/12] extend.texi: Add documentation for __remove_pointer Ken Matsui
2024-03-14 7:22 ` [PATCH v2 12/12] extend.texi: Add subsections for type- and expression-yielding traits Ken Matsui
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=20240314072234.880769-9-kmatsui@gcc.gnu.org \
--to=kmatsui@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=ppalka@redhat.com \
/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).